stolarskis/flood-alert-app

Small app to notify you when its raining.

Flood-Alert-App

More Detailed info + instructions coming soon

App-Flood-App

GRPC Server - Waits for calls from App-Flood-Ctl List of calls that the client can make:

• check-alerts - Requests info from api and checks for severe weather (currently just certain weather codes + rain in the past 3 hours above 3 hours)
• test-alerts - Tests alerts methods - Currently just Text Message and Email
• mute-notifications - mutes notifications of each alert type
  • "Email" mutes email alerts
  • "SMS" mutes SMS alerts (This functionality is changing soon)

App-Flood-Ctl

Small command-line app, that makes requests to the Flood-Server

To make requests locally i'd recommend installing it locally and following the instructions below (once they are finished) The dockerfile is used for the cron job aspect of the project. Its hard coded to make requests to localhost, for use inside the cluster.

Installation:

TODO: Start with how to setup the cluster / setup with gcp

• On your Local Machine: You must have go installed and a running version of the app running
  1. By runing go install the binary will be built and put into your path
  2. run app-flood-ctl to get a list of commands
  3. Before you can make requests locally you must the set the enviroment variable KUBERNETES_IP to the external ip created by the service

App-Flood-Build

Handles creating and populating the kubernetes cluster

CronJob: In order to check requests, kubernetes manages a cronjob that runs the following command app-flood-ctl check-alerts every 30min. This is how the app is able to check alerts.

flood-alert-app's Issues

Add mute alert status to grpc call

In src/api/flood-app-api.proto where muteAlertStatus = true for muted and false for not or however you want to handle it

//Mute SMS = "SMS"
//Mute Email = "Email"
message muteAlertRequest{
  string muteAlertType = 1;
  bool muteAlertStatus = 2;
}

Update the getForecast method to parse more info about the current forecast. Such as temperature, wind speed, other info. Also its spelled forecast not forcast.

Bug with calling API, for some reason is fails to get the info from the server and the entire app crashes. As well as causing the clt to crash.

Double check everything so that no sensitive data is left in any of the repos

github's board doesn't seem to work properly. Unable to move stories from column to column

Implement way for server to store users information

Values returned from flood-app (getForecast) do not reflect the weather outside. Most likely incorrect geographical location entered.

Its pouring outside with a flood watch in effect. Returned summary from getting forecast and it returned "Clear" which is wrong. Possible culprit is entering the wrong lat/long / in the wrong order.

Both main app and ctl need an actual logging file to use. In order to setup logging with kubernetes.

Need to either have each repo have their own logging file/function or have a central logging repo. Right now i'm going with the latter, although it might not be the best way