From e9df802478d04d37de8ed4814693522fddd1607b Mon Sep 17 00:00:00 2001 From: Steve Cliff Date: Fri, 21 Aug 2026 21:01:39 +0100 Subject: [PATCH 1/2] 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.

From a8a6fdfab522f50e12ddc3fda495cf9be2cd4773 Mon Sep 17 00:00:00 2001 From: Steve Cliff Date: Fri, 21 Aug 2026 22:36:14 +0100 Subject: [PATCH 2/2] =?UTF-8?q?docs:=20address=20review=20=E2=80=94=20make?= =?UTF-8?q?=20S3/B2/SFTP/local=20guidance=20actionable?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The previous wording told operators to leave the slot blank and then warned that doing so disables prune, which is contradictory. Prune is gated on the admin slot for every backend, on both paths: scheduled (maintenance_dispatch.go:52) skips silently, manual (repo_ops.go:39) returns 400 admin_creds_required. Also reworded the opening line, which still said 'only needed for rest-server repos' while the new text asks other backends to fill it in. --- web/templates/pages/host_repo.html | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/web/templates/pages/host_repo.html b/web/templates/pages/host_repo.html index f1d5ded..0de5bef 100644 --- a/web/templates/pages/host_repo.html +++ b/web/templates/pages/host_repo.html @@ -82,12 +82,14 @@
✓ saved
{{end}}

- Only needed for rest-server repos that distinguish an append-only - 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. + Required for prune. On rest-server repos this is the + delete-capable user, as distinct from the append-only user used + for everyday backups. Note that forget always + runs with the everyday repo credentials, so those must have + delete authority. For S3 / B2 / SFTP / local, enter the same + delete-capable repository credentials here if you want prune + enabled. Prune is skipped when admin credentials are + unset, on any backend.