Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
This is what my github action is doing currently. Its reading the repo to see if there are any changes, then recreates the docker container and sends it to fly.io. - Then it also creates another container and sends it to dockerhub. When it sends to Fly.io, the website is automatically updated. So any changes on the repo are reflected on the website immediately. Its the same as having a firewall in a linux instance that is guided by the githubaction. Anytime someone makes a change to the file that is in the repo, the firewall gets updates when the instance is recreated. Also if someone deleted the instance the instance would reappear the moment anyone made a change to the repo.
Specifically this link here from github - https://github.com/readme/featured/defining-gitops
From all the comments here, it seems like this is just a github action. Like this one I created already - https://github.com/datakind/aws-tagger/blob/main/.github/workflows/docker-image.yml