This is definitely an over-engineered setup…
I store my Docker Compose files in an internal-only git repo (hosted on Gitea).
Drone is my CI/CD system, and I use Renovatebot to look for updates to container tags (never pull latest
). My workflow is this:
master
) kicks off a Drone workflow that does the following:
git pull
, then docker compose -f "$D" pull
and then docker compose -f "$D" up -d
.I’ve written about step 3 here.
This means I never manually update Docker Compose files, I let Renovate manage everything, I approve PRs, then I walk away and let the scripts run.
I also run a single-node K3s cluster that is hosted on GitHub. Again, using Renovate to open PRs, and I run Flux so watch for changes to master
, which then redeploys applications.
Congrats on the new gig! Six figures has a nice ring to it!
Here are some tips about salary negotiations: