Persist Postfix queue and ship self-contained full backups.

Move the mail queue under /data so recreate no longer drops deferred mail, and archive data/, compose, .env, and certs/ together for restore on a fresh host. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-08-17 14:36:55 +03:00
parent c6a75ce775
commit 41c3e6e896
23 changed files with 408 additions and 170 deletions
@@ -31,6 +31,7 @@ services:
      TLS_KEY_FILE: /etc/postfix/tls/<hostname>.key
    volumes: !override
      - ./data:/data
+      - .:/selfpost-deploy:ro
      # Replace <hostname> with your actual mail/panel hostname, matching
      # the Caddyfile below and SELFPOST_HOSTNAME.
      - ./caddy/caddy-data/caddy/certificates/acme-v02.api.letsencrypt.org-directory/<hostname>:/etc/postfix/tls:ro
@@ -58,6 +58,9 @@ services:
      # kept) so the delivery lines that resolve a queued send-log row survive
      # a container recreate; it is diagnostics and is left out of backups.
      - ./data:/data
+      # Read-only project root for full backups: docker-compose.yml, .env, and
+      # certs/ are archived alongside /data (architecture.md § Persistence).
+      - .:/selfpost-deploy:ro
      # Read-only: SelfPost only ever reads certificates, never manages them
      # (spec 10 p.2). Point this at wherever your reverse-proxy/certbot
      # writes PEM files, e.g. /etc/letsencrypt on the host.
@@ -27,6 +27,7 @@ services:
      # network at selfpost:8080 instead (see nginx.conf.example).
    volumes: !override
      - ./data:/data
+      - .:/selfpost-deploy:ro
      # Same host directory certbot below writes into — plain bind mount,
      # no named volume, so the PEM files are as directly inspectable as in
      # the Apache scenario (spec 10.3).
@@ -17,6 +17,7 @@ services:
      - "587:587"
    volumes: !override
      - ./data:/data
+      - .:/selfpost-deploy:ro
      # Populated by extract-cert.sh from traefik's acme.json — see below.
      - ./traefik/extracted-certs:/etc/postfix/tls:ro
    labels: