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>
112 lines
5.4 KiB
YAML
112 lines
5.4 KiB
YAML
- name: Configure the offsite backup pull
|
|
hosts: backup_store
|
|
gather_facts: yes
|
|
|
|
tasks:
|
|
- name: Ensure the box pulls every source on a timer
|
|
ansible.builtin.include_role:
|
|
name: backup_store
|
|
vars:
|
|
# check-backups.sh reports one result per source plus one for the store
|
|
# itself, so it needs the collection URL and appends each key.
|
|
backup_store_check_push_base: "https://{{ subdomains.gatus }}.{{ root_domain }}/api/v1/endpoints"
|
|
backup_store_check_push_token: "{{ gatus_push_tokens[inventory_hostname] }}"
|
|
backup_store_sources:
|
|
- name: arbret
|
|
source: "arbret@prd-arbret:/opt/arbret/backups/"
|
|
retention_days: 90
|
|
- name: headscale
|
|
source: "backup-pull@headscale.contrapeso.xyz:/opt/backups/headscale/"
|
|
retention_days: 90
|
|
- name: memos
|
|
source: "backup-pull@memos-box:/opt/backups/memos/"
|
|
retention_days: 90
|
|
- name: vaultwarden
|
|
source: "backup-pull@prd-vipy:/opt/backups/vaultwarden/"
|
|
retention_days: 90
|
|
- name: lnbits
|
|
source: "backup-pull@prd-vipy:/opt/backups/lnbits/"
|
|
retention_days: 90
|
|
- name: forgejo
|
|
source: "backup-pull@prd-vipy:/opt/backups/forgejo/"
|
|
retention_days: 14
|
|
# Staging: disposable data, so the long tail is as short as the local one.
|
|
- name: "{{ hostvars['jar_lid_staging_local'].jar_lid_archive_instance }}"
|
|
source: "backup-pull@{{ hostvars['jar_lid_staging_local'].ansible_host }}:/opt/backups/{{ hostvars['jar_lid_staging_local'].jar_lid_archive_instance }}/"
|
|
retention_days: "{{ hostvars['jar_lid_staging_local'].jar_lid_archive_backup_retention_days }}"
|
|
|
|
# ─────────────────────────────────────────────────────────────────────────────
|
|
# Register the backup checks with Gatus.
|
|
#
|
|
# Two groups on purpose, because they answer different questions and fail for
|
|
# different reasons:
|
|
#
|
|
# backup-dump did the SOURCE produce an artefact? Pushed by each dump right
|
|
# after it runs, so a broken dump is visible within minutes.
|
|
# backup-store did it ARRIVE, is it fresh, non-zero, plausibly sized, and is
|
|
# retention pruning? Pushed by check-backups.sh at 05:30.
|
|
#
|
|
# The store alone could catch almost everything, because the artefact filename
|
|
# carries the source's dump timestamp - a source whose timer died still pulls
|
|
# "ok" forever, but the timestamp gives it away. What the source side adds is
|
|
# LATENCY and DIAGNOSIS: the store only learns at the next 04:00 pull, and it
|
|
# cannot tell you whether the dump broke or the pull did.
|
|
#
|
|
# arbret has no dump endpoint: prd-arbret lives in [arbret], which `managed`
|
|
# deliberately excludes, so nothing of ours runs there. It is store-checked only.
|
|
# ─────────────────────────────────────────────────────────────────────────────
|
|
- name: Register the backup checks with Gatus
|
|
hosts: observability
|
|
become: yes
|
|
vars:
|
|
# Sources we deploy the dump for, and the host each one runs on.
|
|
dump_sources:
|
|
- {name: headscale, host: spacey}
|
|
- {name: memos, host: memos_box_local}
|
|
- {name: vaultwarden, host: vipy}
|
|
- {name: lnbits, host: vipy}
|
|
- {name: forgejo, host: vipy}
|
|
- {name: jar-lid-archive-staging, host: jar_lid_staging_local}
|
|
store_sources: [arbret, headscale, memos, vaultwarden, lnbits, forgejo, jar-lid-archive-staging]
|
|
|
|
tasks:
|
|
# 26h, not 7h: the DUMP is genuinely daily, so the window cannot be tighter
|
|
# than a day plus slack. The store-side check catches the same fault within
|
|
# 6h by reading the artefact's dump timestamp out of the filename, so this is
|
|
# the slow backstop rather than the primary signal.
|
|
- name: Build the dump endpoint list
|
|
ansible.builtin.set_fact:
|
|
dump_endpoints: "{{ dump_endpoints | default([]) + [{
|
|
'name': item.name,
|
|
'group': 'backup-dump',
|
|
'token': gatus_push_tokens[item.host],
|
|
'heartbeat': '26h'}] }}"
|
|
loop: "{{ dump_sources }}"
|
|
|
|
- name: Build the store endpoint list
|
|
ansible.builtin.set_fact:
|
|
store_endpoints: "{{ store_endpoints | default([]) + [{
|
|
'name': item,
|
|
'group': 'backup-store',
|
|
'token': gatus_push_tokens['small_backups_local'],
|
|
'heartbeat': '7h'}] }}"
|
|
loop: "{{ store_sources }}"
|
|
|
|
- name: Register the backup endpoints
|
|
ansible.builtin.include_role:
|
|
name: gatus_endpoint
|
|
vars:
|
|
# Push endpoints: the heartbeat window is the tolerance, so alert on
|
|
# the first failure rather than waiting for three 7h windows to pass.
|
|
gatus_endpoint_default_alerts:
|
|
- type: signal
|
|
failure-threshold: 1
|
|
success-threshold: 2
|
|
send-on-resolved: true
|
|
minimum-reminder-interval: 12h
|
|
gatus_endpoint_name: backups
|
|
gatus_endpoint_external: "{{ dump_endpoints + store_endpoints + [{
|
|
'name': 'pull job',
|
|
'group': 'backup-store',
|
|
'token': gatus_push_tokens['small_backups_local'],
|
|
'heartbeat': '7h'}] }}"
|