Our great sponsors
-
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
-
SonarQube
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
-
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
Related posts
- Immutable references in Go?
- Portfolio ideas for backend
- What's a good DNS I can use to filter out all ads on my devices on my network?
- Weird topic: Looking for ideas to make the sys admin job more competitive and inject some adrenaline
- Honeypot Framework: Easy Configuration and Secure Emulation Powered by OpenAI