It’s called CIDR notation

https://en.m.wikipedia.org/wiki/Classless_Inter-Domain_Routing

Ya I’m confused why the GitHub repo isn’t updated to 115 and it’s archived…

The Thunderbird team periodically does this and holds back upgrades for existing installs.

The Flatpak author is waiting for Thunderbird’s approval before publishing 115.

https://github.com/flathub/org.mozilla.Thunderbird/pull/306#issuecomment-1632388273

There’s also Infisical if you don’t want to run Vault

https://github.com/Infisical/infisical

I personally use Ansible to deploy my .env files to my Docker host. The .env files are encrypted in Ansible Vault and deployed to the server as chmod 400 so only I can access them.

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:

1. Renovatebot runs once a night (at midnight) via Drone in a Docker container (I’ve written about this here). If a new image tag is found, it opens a PR in Gitea.
2. I manually log in to Gitea and approve the PR.
3. The PR approval (merging to master) kicks off a Drone workflow that does the following:
   • Runs an Alpine Linux container
   • SSHes from the Alpine Linux container into my Docker host
   • Runs a script (on the Docker host) that basically runs git pull, then docker compose -f "$D" pull and then docker compose -f "$D" up -d.
   • If there is a failure, Drone emails me

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.