mix
5e5d157496
A bounce could be recorded as a successful delivery. The log-tailer's Fixed: - A bounce could be recorded as a successful delivery. The log-tailer's - Log-tailer resumes where it stopped instead of jumping to end-of-file on - Level-2 rate limit no longer overshoots under concurrency: messages that Changed: - The project has a single public home: `github.com/mixeme/selfpost`. Codeberg - Code comments no longer cite the archived specification. References like - `docs/code-review.md` is gone. Its plan is finished — phases 0 (bar the - `docs/architecture.md` gained a *Code layers* section: a diagram of - Phase 1 doc/code hygiene (`docs/code-review.md`): removed ~30 stale … (1 more in CHANGELOG) Security: - Pre-release security review (plan § D, model Fable, 2026-08-06): full pass - `saslpasswd2` argv: the application login is now passed after a `--` Added: - Optional password encryption for the two secret-bearing downloads (plan - Domain import accepts an encrypted export: the envelope is detected by its - `selfpost-backup` writes encrypted archives and reads them back: - `TestParseDelivery` covers the exotic mail.log shapes the review asked for - docs: README *Encrypting a backup or export*; `docs/security.md` § … (14 more in CHANGELOG) Removed: - docs: `security.md` — accepted risk «restore old backup revives session rows» Changed: - docs: `implementation-plan.md` trimmed to the sole open v1.x gate — pre-release - docs: `architecture.md` — sessions (SQLite, idle renew, password change), - docs: `development.md` — expanded e2e stack and `release.yml` matrix workflow. - docs: `security.md` — accepted risk for send-log rows stuck at `queued` after - docs: `roadmap.md` — optional send-log / `mail.log` follow-ups under v1.x tail. … (10 more in CHANGELOG) Full detail: CHANGELOG.md (0.5.0).
46 lines
2.1 KiB
HTML
46 lines
2.1 KiB
HTML
{{define "content"}}
|
|
<h1>Backup & migration</h1>
|
|
|
|
<div class="card">
|
|
<h2>Full backup</h2>
|
|
<p class="muted">Download a full backup of all persistent state — the database,
|
|
every domain's DKIM key and the application credentials. Use it to move the
|
|
whole server to a new machine: restore it into a container of the
|
|
<strong>same SelfPost version</strong>, with the same data mount, before first
|
|
start. TLS certificates and the mail queue are not included.</p>
|
|
<p class="muted"><strong>The backup file is a secret</strong> (it contains
|
|
private keys and credentials). Store and transfer it securely and delete it
|
|
once the restore succeeds. Encrypting it below is the simplest way to do that:
|
|
the download is then a <code>.spbk</code> file that only the password opens.</p>
|
|
{{if .BackupErr}}<p class="error">{{.BackupErr}}</p>{{end}}
|
|
<form method="post" action="/backup">
|
|
{{template "encryptfields" .}}
|
|
<button type="submit">Download full backup</button>
|
|
</form>
|
|
</div>
|
|
|
|
<div class="card">
|
|
<h2>Import a domain</h2>
|
|
<p class="muted">Move a single domain here from another SelfPost instance using
|
|
a domain export file (from that domain's page). Its DKIM key and application
|
|
passwords come across, so the published DNS record needs no change. The export
|
|
file is a secret, like a full backup.</p>
|
|
{{if .ImportErr}}<p class="error">{{.ImportErr}}</p>{{end}}
|
|
<form method="post" action="/domains/import" enctype="multipart/form-data">
|
|
<label for="importfile">Domain export file</label>
|
|
<input id="importfile" name="file" type="file" accept=".json,.spde,application/json" required>
|
|
<div class="encrypt">
|
|
<label class="check">
|
|
<input type="checkbox" data-encrypt-toggle>
|
|
<span>The file is encrypted (<code>.spde</code>)</span>
|
|
</label>
|
|
<div class="encrypt-fields" data-encrypt-fields>
|
|
<label for="importpw">Password</label>
|
|
<input id="importpw" name="import_password" type="password" autocomplete="off">
|
|
</div>
|
|
</div>
|
|
<button type="submit">Import domain</button>
|
|
</form>
|
|
</div>
|
|
{{end}}
|