Debian
dbc14a24a4
feat(backup): Restore-Pfad — POST /backups/:id/restore + UI
backup.Service.Restore(id) schreibt /var/lib/edgeguard/restore.sh
und dispatcht via `sudo systemd-run --unit=edgeguard-restore.service`.
Skript-Ablauf:
1. tar -xzf der Backup-Datei → /var/lib/edgeguard/restore-tmp
2. state-files (setup.json/license/jwt/node.conf/acme-account) per
cp -a zurück, chown edgeguard
3. systemctl stop edgeguard-api + scheduler (DB-Connections freigeben)
4. sudo -u postgres psql -f dump.sql (--clean droppt + recreated)
5. edgeguard-ctl render-config (haproxy/nft/squid/unbound/chrony)
6. systemctl start edgeguard-api + scheduler
7. rm -rf restore-tmp + restore.sh
UI: pro Backup-Row neuer Restore-Button mit Popconfirm. Beim Trigger
zeigt sich das vertraute Fullscreen-Overlay (Klassen .update-modal*
re-used) mit 4 Steps (Extract / DB-Restore / Render / Restart) + Live-
Timer. Health-Poll alle 3s detektiert API-Restart + reload. Safety-
Timeout 3 min für große DB-Dumps.
postinst: sudoers für `systemd-run --unit=edgeguard-restore.service
--description=... --collect bash /var/lib/edgeguard/restore.sh` +
zugehöriges `systemctl reset-failed`. Pfad fix damit kein Wildcard
nötig wird.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 23:22:55 +02:00
..
2026-05-09 21:49:14 +02:00
2026-05-11 07:46:39 +02:00
2026-05-11 21:51:09 +02:00
2026-05-11 20:55:47 +02:00
2026-05-12 23:22:55 +02:00
2026-05-10 22:50:00 +02:00
2026-05-09 21:49:14 +02:00
2026-05-09 10:59:52 +02:00
2026-05-11 06:24:51 +02:00
2026-05-09 09:56:10 +02:00
2026-05-10 18:05:27 +02:00
2026-05-12 21:05:39 +02:00
2026-05-11 00:27:05 +02:00
2026-05-09 16:08:44 +02:00
2026-05-11 13:41:16 +02:00
2026-05-10 16:19:07 +02:00
2026-05-11 06:58:54 +02:00
2026-05-09 10:59:52 +02:00
2026-05-10 20:51:25 +02:00
2026-05-09 09:56:10 +02:00
2026-05-09 09:56:10 +02:00
2026-05-12 21:29:38 +02:00
2026-05-09 21:49:14 +02:00
2026-05-10 21:07:38 +02:00
2026-05-08 18:45:41 +02:00