connor
e6644d0616
Replaces the previous repo, which had split into two histories that never met (mainframe on a dead GitLab remote, the laptops on Gitea) with 146 dirty files across three machines and the NAS never enrolled at all. Branch-per-machine is gone. One main, with host differences expressed as small files under hosts/<hostname>/ rather than as branches, so there is nothing to merge. The reconciled zsh layer reduces 15-33 line forks to 1-7 effective lines per host; distro differences (oh-my-zsh prefix, syntax-highlighting path, fd vs fdfind) are probed in common/ instead. Fresh history: the old one carried six plaintext credentials, 45 MB of mail caches, browser caches and vendored binaries. 5,096 tracked files and 144 MB become 462 files and 2.6 MB. The .gitignore is now an allowlist, which is what keeps that true. Root cause of the rot: ~/.local/bin was a symlink to scripts/ with GOPATH inside it, so every go install wrote into version control (2.2 GB on the work laptop). PATH now points at the repo instead of the reverse. Also: Hyprland replaces sway and is sourced in two halves so $browser is defined before use; singleton automations carry ConditionHost= alongside host-layer-only placement; ddns moves from cron to a guarded timer; package manifests and pkg-snapshot/pkg-restore replace the X11-era install_scripts/; networkmanager-dmenu added to system76 (the binding always existed, the package never did).
1.4 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| podman-compose-bind-mount-restart | podman-compose up -d does NOT restart a container when only a bind-mounted config file changed — use podman restart |
|
In Connor's stack (/home/connor/compose.yml, rootful podman), podman-compose up -d <service> only recreates a container when the service definition in
compose.yml changes. Editing a bind-mounted config file — e.g.
config/authelia/configuration.yml, config/litellm/config.yaml,
config/llama-swap/config.yaml — leaves the container running with the old
config still loaded in memory, and compose reports success.
Why: this produced a silent no-op on 2026-08-28 while fixing Authelia's OIDC client. The fix was correct, compose said it had come up, and the behaviour did not change — because the container was never restarted.
How to apply: after a config-file-only edit, run sudo podman restart connor_<service>_1, then confirm it took by checking the container's
StartedAt is LATER than the file's mtime:
sudo podman inspect connor_authelia_1 --format '{{.State.StartedAt}}'
stat -c %y config/authelia/configuration.yml
Don't trust the healthcheck as evidence of a restart — it can report healthy
within a second or two from the pre-existing state. llama-swap is the exception:
it polls its own config every 2s and reloads itself.
Related: zen-tos-hold