halkyon/deploy/backup/halkyon-backup.timer

# Starts halkyon-backup.service at the start of every hour; the run at 03:00,
# the server's time (Europe/Berlin), also prunes and checks, done before the security
# updates may reboot at 04:00. A run missed while the server was off happens as soon as
# it is back. Installed as /etc/systemd/system/halkyon-backup.timer.
[Unit]
Description=Hourly off-site backup of learn.halkyon.eu

[Timer]
OnCalendar=hourly
Persistent=true

[Install]
WantedBy=timers.target
feat(deploy): hourly off-site backups with restic learn.halkyon.eu dumps its database every hour (people's files are in it too) and restic stores the dump encrypted in a Hetzner Storage Box, keeping 24 hourly, 7 daily, 4 weekly and 3 monthly snapshots. The box's own snapshots, removable only in Hetzner's Console, protect the backups from a taken-over server. A systemd timer runs it as deploy; once a day it also prunes and checks the repository. Failures go to the journal. Hourly, because a restore costs people who started after the backup what their device held: the app no longer finds its session and starts anew. deploy/backups.md describes the setup, the restore and what a restore loses; both were rehearsed on the local Compose stack. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me> 2026-10-03 16:45:40 +02:00			`# Starts halkyon-backup.service at the start of every hour; the run at 03:00,`
chore: the servers are named by the domain they serve Files called the servers by their own host names, which are the operator's and say nothing a reader needs. They now say which domain a server serves: learn.halkyon.eu's server (the instance and its CI runner), the halkyon.app server (Forgejo and the F-Droid repository). Two names are settings rather than words. CI's runner label becomes `instance` (`runs-on: instance`, `labels: ["instance:host"]`): the runner reads its installed copy of deploy/runner/config.yml, so jobs wait in the queue until that copy is updated and the runner restarted. The SSH aliases the scripts and docs use become `learn-deploy` and `fdroid-upload`. AGENTS.md says to keep it so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me> 2026-10-13 23:11:40 +02:00			`# the server's time (Europe/Berlin), also prunes and checks, done before the security`
			`# updates may reboot at 04:00. A run missed while the server was off happens as soon as`
feat(deploy): hourly off-site backups with restic learn.halkyon.eu dumps its database every hour (people's files are in it too) and restic stores the dump encrypted in a Hetzner Storage Box, keeping 24 hourly, 7 daily, 4 weekly and 3 monthly snapshots. The box's own snapshots, removable only in Hetzner's Console, protect the backups from a taken-over server. A systemd timer runs it as deploy; once a day it also prunes and checks the repository. Failures go to the journal. Hourly, because a restore costs people who started after the backup what their device held: the app no longer finds its session and starts anew. deploy/backups.md describes the setup, the restore and what a restore loses; both were rehearsed on the local Compose stack. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me> 2026-10-03 16:45:40 +02:00			`# it is back. Installed as /etc/systemd/system/halkyon-backup.timer.`
			`[Unit]`
			`Description=Hourly off-site backup of learn.halkyon.eu`

			`[Timer]`
			`OnCalendar=hourly`
			`Persistent=true`

			`[Install]`
			`WantedBy=timers.target`