dewberry / nwm-forecasts Goto Github PK

Could be in the form of a csv, json, or small sqlite db. This can be read in to the Go code and translate for the user

Add a workflow that will update the DockerHub readme with the GitHub readme every time there is a push to master or a new docker build/push

Current output is:

"medium_range":{
    "2020-08-02-15":
        [
            {"comid_index":900,"flow":4.71},
            {"comid_index":900,"flow":4.71},
            {"comid_index":900,"flow":4.71},
            {"comid_index":900,"flow":4.71},
            {"comid_index":900,"flow":4.71},
            {"comid_index":900,"flow":4.71},
            {"comid_index":900,"flow":4.71}
        ],
"2020-08-02-18":[{ "......"

Where each item in the date array represents members 1-7 in order. These need labels.

It looks like only the main executable is copied over to the final build. Where does the goo

Right now we have .gitkeep files in the two directories, but If someone wanted run this by pulling only the image, not building it, where would the main executable mount the goofys buckets? I think there either needs to be a make dirs call in the Go code, or the docker file needs to make the necessary directories in the second stage of the build.

I am going to test this shortly by running:

docker run dewberrycsi/nwm-fetch-forecasts:latest

The medium range forecast is only available 4 times a day (00, 06, 12, 18, 24)

The start/end date for requests drawing from the retrospective is fixed at 5 days before/after. This should be dynamically requested by the user.