systemd service

Mon, 01 Jan 0001 00:00:00 +0000

perch serve runs in the foreground, logs to stderr, drains connections on SIGTERM/SIGINT (waiting up to five seconds), and reloads certificate files on SIGHUP, so it maps directly onto a Type=simple unit. It does not fork, write a PID file, implement sd_notify, or support socket activation; do not use Type=notify or socket units.

The examples below use a dedicated perch service account, /etc/perch/perch.yaml, and /var/lib/perch. Adjust paths if your layout differs, and keep data_dir in YAML in sync with StateDirectory and ReadWritePaths.

Backup and garbage collection

Mon, 01 Jan 0001 00:00:00 +0000

perch gc and perch backup are one-shot commands and are safe to run while perch serve is running: SQLite WAL mode allows concurrent readers and writers.

perch reconcile does not need a timer. serve reconciles S3 at startup and every storage.s3.reconcile_every (default 5m).

Backup timer

perch backup refuses to overwrite an existing destination. Use a wrapper to add timestamps and prune old copies. Write /usr/local/bin/perch-backup:

sudo tee /usr/local/bin/perch-backup >/dev/null <<'EOF'
#!/bin/sh
set -eu
stamp=$(date +%Y%m%d-%H%M%S)
/usr/local/bin/perch backup --config /etc/perch/perch.yaml "/var/lib/perch/backups/perch-$stamp.db"
find /var/lib/perch/backups -type f -name 'perch-*.db' -mtime +14 -delete
EOF
sudo chmod 0755 /usr/local/bin/perch-backup

/etc/systemd/system/perch-backup.service:

Operations on perch docs

systemd service

Backup and garbage collection

Backup timer