Runbooks: the scripts/ move (PR #749) and the retired tools (PR #748) - ops_lock and shutdown_mode run as `python -m caper.<module>` from /srv/caper. Operator-lock gains a section on checkouts from before the move, and on the one deploy that crosses it (lock taken the old way, released the new way). - start-server.sh is at scripts/deploy/; the root stop-server.sh is gone, and the dev page names the two commands it ran. - Script paths under /srv/scripts/{diagnostics,maintenance}/; the backup cron line uses `-m caper.backup_sqlite`. - check_volume_reclamation.py, rebuild_version_chains.py and repair_head_chain_fields.py are retired; the reclamation answer (no) and how to re-check it are kept on How-backups-work, and the I9 entry is dropped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C3qw3gotMvPgGSJp5Tb2xe
Operator lock: on prod since v4.9.0_110626
Add the operator lock page and put the lock in the deploy runbooks Deploys take the lock first and release it last, using `acquire` because a restart kills `run` inside the container. These commands ran on dev on 2026-11-06. Prod gets the lock with the first release after v4.8.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C3qw3enZCA1p5BESZYvFWG
Deploy runbooks: toggle shutdown mode from a shell with shutdown_mode.py
Deploying to dev: what a requirements.txt change actually does, and how to recover Recorded from an occurrence on 2026-09-04. The page already said dependency changes need an image rebuild; this adds what happens if you do it anyway, because the failure is confusing and the obvious fixes make it worse: * app packages live in /opt/venv, so a plain 'pip3 install' in the container targets the wrong interpreter and silently pulls a newer major Django * a crash-looping container cannot be exec'd into; the recovery is to boot an older commit first * --no-deps trades one crash loop for another when a transitive dep is missing * stop-and-start-repo.sh keeps the writable layer, start-server.sh does not -- which is why a hand-installed dependency works until someone recreates the container
Add the Development Server page: what dev is for, the landing-page passphrase, and how to request an account The dev home page now shows a landing gate (AmpliconRepository #619) that links here for the passphrase and for account requests.
Add Storage cleanup tools runbook, and link it from Home Which tool answers which question, how to run one inside either container, how to read a validator failure, and the four-step procedure for a write to production. No current-state figures: the page names the command that prints each number instead of quoting one that goes stale.
Record how to check whether the deleted storage came back The question gets asked again every few weeks and the answer depends entirely on reading the metric the right way: the plateau, not the current value, and never collStats. check_volume_reclamation.py does the reading; this says how to interpret it and which two mistakes it exists to prevent.
The reference builds now have a verified copy off AWS Taken 2 Sep 2026: all ten tarballs downloaded and checked against the md5sums published beside them in the bucket. That was the last single copy of anything this site depends on, so it comes off the uncovered list on both pages.
Add a page describing how backups actually work The off-site page covers the copies a person takes by hand. Nothing described the system: which mechanism protects which store, the policy decisions and the reasoning behind them, how to restore and what the restore looks like while it is running, and how to tell any of it is working. Also corrects the metadata dump size on the off-site page: it is ~39 MiB now, not ~51, because fs.files fell from 1,065,009 rows to 808,532 when the GridFS residue was swept.
Correct the API section against the real endpoints, and index the wiki
Off-site backups: the procedure for the copies that leave AWS
Updated Home page may temporarily link to an older project version (markdown)
Created Home page may temporarily link to an older project version (markdown)
Created Deploying unreleased code to dev (markdown)
Updated Creating a new release for AmpRepo (markdown)
Created Updating the data repo (markdown)
Updated Updating the Dev & Prod servers (markdown)
adding details on making the release
Created dev.ampliconrepository.org instructions (markdown)
Updated SQLite DB errors you might run into (markdown)
Created SQLite DB errors you might run into (markdown)
Updated dev.ampliconrepository.org instructions (markdown)
Updated Database details (markdown)
Updated DB layout (markdown)
Created DB layout (markdown)
Updated config file requirements (markdown)