search

technologiestiftung / giessdenkiez-de-dwd-harvester

Gather precipitation data from DWD's radolan data set, for the region of Berlin and connect to the trees DB
https://www.giessdenkiez.de
MIT License
4 stars 9 forks source link

Housekeeping: Remove ecs and fargate legacy code #92

Open sjockers opened 1 year ago

sjockers commented 1 year ago

There's a provisioning script for ECS in this repo and a reference to Fargate in the readme. Is this actually meant to be used or is it legacy code/infrastructure? My understanding was that the resulting Docker image is used in this GH workflow. Or am I missing something?

sjockers commented 1 year ago

Also, maybe related, I was wondering why the cron schedule is commented out for the harvesters – e.g. here: https://github.com/technologiestiftung/giessdenkiez-de/blob/master/.github/workflows/rain.yml#L7-L8

ff6347 commented 1 year ago

Yes the fargate/ecs stuff is legacy code and can be removed. We had it first running as aws fargate but moved it to GitHub Actions for more transparency.

Also, maybe related, I was wondering why the cron schedule is commented out for the harvesters – e.g. here: technologiestiftung/giessdenkiez-de@master/.github/workflows/rain.yml#L7-L8

The cron schedule is commented out because we use repository_dispatch actions. If a repo development is stale (no commits happening) a schedule action is paused after 60 (or was it 90) days. We moved to cronjobs running on pipedream.com using repo dispatch to be sure that all jobs keep running.