mixandClaude Opus 5.5
8c9a71e6a0
Found by the e2e restore scenario of the next commit: the Full backup button answered 200 with ten bytes. The archive includes the Postfix queue, Postfix keeps every queue file and directory readable by its own user alone (not configurable), and the panel runs as its own user - the walk stopped at /data/postfix/queue/active with "permission denied" after the headers were out. So since the queue moved under /data in 1.3.0. Confirmed on the test server: selfpost-backup as root makes the whole archive, the same command as user panel fails the same way. Owner, 2026-10-11: the panel's archive comes without the queue. - backup.Params.Unprivileged: the queue is left out, and so is a file under certs/ that cannot be opened (the private key on the test server is root and Postfix's group only), named through OnWarn. The selfpost-backup command leaves it unset and takes both, as before. - backup.Check reads through everything Create would archive, writing nothing. The panel runs it before the first byte: a failure is a message on the page, not a download cut short. - The box, Help (design commit before this one) and the guide say what the panel's archive leaves out; the guide's comparison table has rows for the queue and the private key, and tells to put the key back before starting a restored instance. go vet ./internal/backup/ ./internal/web/handlers/: ok go test ./internal/backup/ ./cmd/... ./internal/web/...: ok make e2e on the test server, with the restore scenario: ok Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
49 lines
3.4 KiB
HTML
49 lines
3.4 KiB
HTML
{{/* Backup (mockup backup.html): the whole instance in one archive, and one
|
|
domain brought in from another SelfPost. Two boxes, each its own form and
|
|
its own POST; a refusal of either comes back as the flash above them. The
|
|
password fields of the full backup are shown when the box is ticked (panel.js
|
|
reads data-encrypt-toggle / data-encrypt-fields); the import asks for a
|
|
password only for an encrypted file (data-import-file /
|
|
data-import-password-fields). Without scripts all of them are visible. */}}
|
|
{{define "content"}}
|
|
{{template "page_head" .Head}}
|
|
{{if .Flash}}{{template "flash" .Flash}}{{end}}
|
|
|
|
<div class="columns">
|
|
<div class="column is-6">
|
|
{{template "box_open" .Full}}
|
|
{{template "body_open"}}
|
|
<p class="mb-3"><code>data/</code> (database, DKIM keys, credentials), <code>docker-compose.yml</code>, <code>.env</code> and <code>certs/</code> in one archive, without the Postfix queue and without a certificate file the panel may not read. Restore into an empty project directory and start the <strong>same SelfPost version</strong>. The reverse-proxy vhost is not included.</p>
|
|
<form class="sp-form" method="post" action="{{.FullAction}}">
|
|
<div class="field"><label class="checkbox"><input type="checkbox" name="encrypt" value="1"{{if .Encrypt}} checked{{end}} data-encrypt-toggle> Encrypt with a password (<code>.spbk</code>)</label></div>
|
|
<div data-encrypt-fields>
|
|
<div class="sp-pair">
|
|
<div class="field"><label class="label" for="encpw">Password</label><div class="control"><input class="input" id="encpw" name="password" type="password" autocomplete="new-password" minlength="{{.PasswordMin}}" placeholder="at least {{.PasswordMin}} characters"></div></div>
|
|
<div class="field"><label class="label" for="encpw2">Repeat password</label><div class="control"><input class="input" id="encpw2" name="password_confirm" type="password" autocomplete="new-password"></div></div>
|
|
</div>
|
|
<p class="help mb-3">Keep this password: SelfPost does not store it, and the file cannot be opened without it.</p>
|
|
</div>
|
|
<button type="submit" class="button is-primary"><i class="ti ti-download"></i>Download full backup</button>
|
|
</form>
|
|
{{template "body_close"}}
|
|
{{template "box_close"}}
|
|
</div>
|
|
|
|
<div class="column is-6">
|
|
{{template "box_open" .Import}}
|
|
{{template "body_open"}}
|
|
<p class="mb-3">A domain export from another instance — plain <code>.json</code> or encrypted <code>.spde</code>. Its DKIM key and application passwords come across, so the published DNS needs no change. The export itself is made on the domain's settings page.</p>
|
|
<form class="sp-form" method="post" action="{{.ImportAction}}" enctype="multipart/form-data">
|
|
<div class="field"><label class="label" for="importfile">Domain export file</label>
|
|
<div class="control"><input class="input" id="importfile" name="file" type="file" accept=".json,.spde,application/json" required data-import-file></div></div>
|
|
<div class="field" data-import-password-fields><label class="label" for="importpw">Password</label>
|
|
<div class="control"><input class="input" id="importpw" name="import_password" type="password" autocomplete="off"></div>
|
|
<p class="help">Asked only for an encrypted <code>.spde</code> file.</p></div>
|
|
<button type="submit" class="button is-primary"><i class="ti ti-file-import"></i>Import domain</button>
|
|
</form>
|
|
{{template "body_close"}}
|
|
{{template "box_close"}}
|
|
</div>
|
|
</div>
|
|
{{end}}
|