https://git-scm.com/docs/git-diff#Documentation/git-diff.txt---color-movedltmodegt

https://medium.com/pragmatic-programmers/git-config-diff-colormoved-8e2f24af6645

From their FAQ. So it seems there are free 802.11n APs…

If the device has a DSL modem or an 802.11ac wifi chipset, the libreCMC project can’t support these devices. There are currently no fully free (libre) 802.11ac or DSL modem chipsets

Are there open source APs? I was under the impression that everything required binary firmware (even if running something like OpenWrt).

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

I like Flatpaks for running proprietary software (Slack, Discord, Spotify) because I can use Flatseal to lock down permissions for each app.

I also agree with someone else that said Flatpaks don’t really integrate well when they need deep system integration.

I really like that Flathub now has a verified section (as opposed to some random person packaging the application).

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.

This is the correct answer.