jar-lid-archive: a staging deployment on its own box

Jar Lid Archive (Django + Postgres 18 + SeaweedFS) on jar-lid-archive-staging-box
(nodito VM 3300, 1 core / 1 GB / 10 GB), public at jars-staging.contrapeso.xyz
through vipy's Caddy. New role roles/jar_lid_archive; per-host values in
host_vars, so a production host is a new [jar_lid_archive] entry, not a new
playbook.

── Containers, following :master ──────────────────────────────────────────
The same three services as the app repo's compose.yaml, so staging rehearses
what dev and CI run. Every playbook run pulls :master and `up -d --wait`s;
compose recreates web only when the digest moved. --wait gates on web's
/health/, which checks the database and the bucket, so a green run means the
app serves. Upgrading is re-running the playbook.

── web is on the host network ─────────────────────────────────────────────
Docker's published ports are DNATed before UFW sees them, so `8000:8000` would
answer on the LAN whatever UFW says, and binding to the tailnet IP races
tailscaled at boot. On the host network gunicorn's port is an ordinary one: UFW
default-deny covers the LAN, tailscaled's ts-input accepts tailscale0 ahead of
UFW (checked on mempool-box), and the headscale ACL grants tag:prd-vipy exactly
:8000. db and storage publish on 127.0.0.1 only. Verified: LAN times out, vipy
gets 200.

That matters for HTTPS: the app trusts X-Forwarded-Proto
(DJANGO_BEHIND_TLS_PROXY=1), which is only safe while Caddy is the sole client.
Login POST through the public URL passes CSRF; cookies are Secure.

── Secrets ────────────────────────────────────────────────────────────────
Generated straight into host_vars/jar_lid_staging_local/vault.yml, never
printed: Django key, Postgres and S3 secrets, and seed passwords for the
fixture's alice/bob/admin usernames - never the fixture's published passwords,
since the site is public. The group vault gains one line, this host's Gatus push
token; decrypted, it differs from before by exactly that line.

── Backups, and the outage the first one caused ───────────────────────────
One uncompressed tar (pg_dump -Fc + the SeaweedFS data dir), age-encrypted on
the box at 02:20, pulled by small-backups-box; 3 days at both ends. Verified end
to end, including decrypting a pulled artefact on lapy.

The first test run stopped web AND storage and left the app down 26 minutes:
SeaweedFS outlasted its 150s healthcheck budget on this disk, compose marked it
unhealthy, and web's depends_on never started it. Now only web is stopped - it
is the only writer to both stores, so they are still captured at one instant -
and the healthchecks have start_periods sized for the disk.

Also inherited from the app's compose.yaml: storage writes /tmp/s3.json and
chowns it to seaweed, so on a RESTART of the same container root cannot
re-create it (sticky /tmp + protected_regular): "Permission denied". Fixed here
with rm -f first; the app repo needs the same line.

── The disk is the problem ────────────────────────────────────────────────
The VM disk is on proxmox-tank-1, the HDD mirror, which knots-box's random reads
(~6 MB/s) keep near saturation. Inside this VM: ~96% "full" I/O pressure while
idle, ~5 min to start web, sudo occasionally over 12s. Moving it to local-zfs
(NVMe) is the fix; noted in the README, not done.

── Also ───────────────────────────────────────────────────────────────────
- lan_ip read from the Proxmox guest agent; host key checked against the one
  the agent reads off the disk before it went into known_hosts.
- Monitoring: liveness + disk (400), probe_jar-lid-archive-staging (403), public
  /health/ + DNS (402), backup-dump/backup-store.
- tofu: the VM definition.
- Deployed v2026.10.03.1.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

ansible/services/jar-lid-archive/setup_backup_jar_lid_archive.yml

@@ -0,0 +1,34 @@
+---
+# Jar Lid Archive backup: the database and the photo store, as ONE artefact,
+# dumped and age-encrypted on the box itself. small-backups-box pulls it.
+#
+# Only `web` is stopped. It is the only writer to both the database and the
+# photo store, so with it down both are quiescent and are captured at the same
+# instant - no row points at a photo the tar lacks. db stays up for pg_dump.
+#
+# storage is deliberately NOT stopped, though an earlier version did: on this
+# VM's contended HDD-backed disk SeaweedFS can take minutes to come back, and the
+# first test run left the app down for 26 minutes waiting on it.
+- name: Configure the Jar Lid Archive backup on its own host
+  hosts: jar_lid_archive
+  become: yes
+
+  tasks:
+    - name: Ensure Jar Lid Archive dumps itself, encrypted, on a timer
+      ansible.builtin.include_role:
+        name: backup_source
+      vars:
+        backup_source_name: "{{ jar_lid_archive_instance }}"
+        backup_source_description: "Jar Lid Archive ({{ jar_lid_archive_instance }})"
+        backup_source_dump_command: /usr/local/bin/jar-lid-archive-dump.sh
+        # Uncompressed: the bulk is JPEGs. See roles/jar_lid_archive/templates/dump.sh.j2.
+        backup_source_artifact_suffix: "tar.age"
+        backup_source_stop_command: "docker compose -f /opt/jar-lid-archive/docker-compose.yml stop web"
+        # `up -d --wait`, not `start`: it also repairs a db or storage that died
+        # meanwhile, and only returns once /health/ passes.
+        backup_source_start_command: "docker compose -f /opt/jar-lid-archive/docker-compose.yml up -d --wait --wait-timeout 300"
+        backup_source_retention_days: "{{ jar_lid_archive_backup_retention_days }}"
+        backup_source_on_calendar: "*-*-* 02:20:00"
+        # Reported to Gatus as backup-dump_<instance>.
+        backup_source_push_url: "https://{{ subdomains.gatus }}.{{ root_domain }}/api/v1/endpoints/backup-dump_{{ jar_lid_archive_instance }}/external"
+        backup_source_push_token: "{{ gatus_push_tokens[inventory_hostname] }}"