server restore: an archive checked, dry-run, and put back — configuration with modes and owners, the store in SQLite or PostgreSQL; backup_copy_to copies archives off the machine

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Ilker ManapandClaude Opus 5.5 committed 2026-10-04 23:09:59 +02:00
1 parent d29f694aaf
commit 10466416df
11 files changed
+889 -25

No files matched your search

+19
View File
@@ -245,6 +245,8 @@ rather than repeated.
| `notify` | `notify.Config` | [Server](#server) |
| `firewall_networks` | `[]string` | [Server](#server) |
| `backup_recipients` | `[]string` | [Server](#server) |
| `backup_copy_to` | `[]string` | [Server](#server) |
| `backup_copy_key` | `string` | [Server](#server) |
| `releases` | `string` | [Server](#server) |
| `router` | `Router` | [Server](#server) |
| `control` | `Control` | [Server](#server) |
@@ -2008,6 +2010,23 @@ the certificate authority's key and every secret in the store, and is
copied off the machine; encrypted, the copy is safe wherever it lands.
Empty writes archives unencrypted, readable by root only.
### `backup_copy_to`
`[]string`
BackupCopyTo is where each archive is copied once written, so it
survives this machine: a directory (a mounted share, another disk) or
ssh://user@host[:port]/path, reached with BackupCopyKey and checked
against /etc/llmgw/backup_known_hosts, which learns a host the first
time. The same number of archives is kept there as here. Refused
without backup_recipients: an archive leaves the machine encrypted.
### `backup_copy_key`
`string`
BackupCopyKey is the SSH private key for ssh:// copies.
### `releases`
`string`