install: run again, it keeps the options it isn't given (#84) #85

Merged
jcoffey-dev merged 2 commits from fix/84-install-reuses-record into main 2026-11-18 17:03:01 +00:00
2 Commits
Author SHA1 Message Date
jcoffey-dev 1389ca9a2c install: reload Caddy when a re-run changes its configuration
ci / test (pull_request) Successful in 1m14s
compose.Write rewrites the Caddyfile on every run, but Caddy reads it only
at start, and a changed bind-mounted file doesn't make compose recreate
the container. So a re-run with new names, or with a front end added or
taken off, left Caddy serving and certifying the old ones: after a rename
the new console name didn't answer and the new mail host's HTTP-01
challenge was redirected instead of reaching the server (found by the
rename e2e case). A converge that changed the Caddyfile now runs caddy
reload, and restarts Caddy if the reload doesn't take.
2026-11-18 09:44:39 -07:00
jcoffey-dev 6787289bb9 install: run again, it keeps the options it isn't given (#84)
Running install on a machine with an install recorded started from the
defaults, so an option left out changed the install: a missing --server
host asked for a move, a missing --proxy snippets swapped in Caddy, and
renaming meant repeating every option from the first run.

Now every option not on the command line or in --answers is taken from
the install: shapes (a component it doesn't have stays skipped), proxy,
names, dir, ACME contact and CA. The record gains the proxy, the front
ends' names and the ACME settings; for installs from before it, the proxy
is read from the deployment's files and the front ends' names from the
addresses the server is given (INBUXA_ADMIN_URL / INBUXA_WEBMAIL_URL).
The plan lists what it took. Front ends joined to a server elsewhere
inherit nothing.
2026-11-18 09:30:20 -07:00