Skip to main content

max / makenotwork

sando: name the scratch DB user explicitly in the config example An unqualified scratch_db_url (no user) peer-auth-fails under sqlx in a minimal systemd env, which resolves the missing user to "anonymous" rather than the OS user. That crash-looped sandod at the startup scratch preflight on the 0.2.3 self-update; --check-config can't catch it (no DB connect). Bake &user=sando into the example so a fresh install can't reintroduce it.
Co-Authored-By
Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-07-25 13:02 UTC
Signed with PGP, not checked
Commit: c430bc1e8c689417babaa761d72f1a4ce198e509
Parent: e8fa21e
1 file changed, +6 insertions, -1 deletion
@@ -18,7 +18,12 @@
18 18 build_host = "fw13"
19 19 workdir = "/srv/sando/work"
20 20 release_root = "/srv/sando"
21 - scratch_db_url = "postgres:///sando_scratch?host=/var/run/postgresql"
21 + # Name the user explicitly. libpq (psql) defaults a missing user to the OS user,
22 + # but sqlx in a minimal systemd env (no USER/LOGNAME) defaults it to "anonymous",
23 + # so an unqualified URL peer-auth-fails and crash-loops sandod at the startup
24 + # scratch preflight (--check-config does not catch it — no DB connect). See the
25 + # maintainer notes / memory reference_sando_scratch_db.
26 + scratch_db_url = "postgres:///sando_scratch?host=/var/run/postgresql&user=sando"
22 27 bin_names = ["makenotwork", "mnw-admin"]
23 28 logs_root = "/srv/sando/logs"
24 29 # Shared cargo target dir across per-sha worktrees. Without it every /rebuild