mix
f62fe23826
The first MINOR after 1.0.0: send-only DMARC guidance in the panel, AGPL packaging on every page, and an internal split of `internal/web` ahead of domain-admin work. Upgrading runs one SQLite migration (empty defaults; existing DNS guidance is unchanged until you set a report address). Changed: - `internal/web` split into subpackages (`web/view`, `web/auth`, `web/validate`, Added: - panel: DMARC guidance for send-only relays — the suggested `_dmarc` record - AGPL packaging hygiene: [NOTICE](NOTICE) names the copyright holder and the - [docs/roadmap.md](docs/roadmap.md) — candidate item **visual-style** (panel Full detail: CHANGELOG.md (1.1.0).
42 lines
2.0 KiB
HTML
42 lines
2.0 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 (SelfPost backup) 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) — plain <code>.json</code> or
|
|
encrypted <code>.spde</code> (SelfPost domain export). 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 data-import-file>
|
|
<div class="encrypt-fields" data-import-password-fields>
|
|
<label for="importpw">Password</label>
|
|
<input id="importpw" name="import_password" type="password" autocomplete="off">
|
|
</div>
|
|
<button type="submit">Import domain</button>
|
|
</form>
|
|
</div>
|
|
{{end}}
|