From e9df802478d04d37de8ed4814693522fddd1607b Mon Sep 17 00:00:00 2001 From: Steve Cliff Date: Fri, 21 Aug 2026 21:01:39 +0100 Subject: [PATCH] docs: correct admin-credentials help text MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Forget does not use admin credentials. Only JobPrune builds a runner against the admin slot (cmd/agent/main.go:622-645); JobForget runs on the everyday runner, as the comment at main.go:517-524 states. Also corrects the claim that leaving this blank lets everyday creds handle prune: maintenance_dispatch.go:52-56 skips prune entirely with 'prune skipped — no admin creds' on any backend, with no fallback. Refs #34 --- web/templates/pages/host_repo.html | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/web/templates/pages/host_repo.html b/web/templates/pages/host_repo.html index ebfb7cf..f1d5ded 100644 --- a/web/templates/pages/host_repo.html +++ b/web/templates/pages/host_repo.html @@ -83,9 +83,11 @@ {{end}}

Only needed for rest-server repos that distinguish an append-only - user (everyday backups) from a delete-capable user (prune / - forget). For S3 / B2 / SFTP / local, leave this blank — the - everyday repo credentials handle prune too. + user (everyday backups) from a delete-capable user (prune). Note + that forget always runs with the everyday repo + credentials, so those must have delete authority. For S3 / B2 / + SFTP / local, leave this blank — but note that prune is + skipped entirely when this is unset, on any backend.