Running install again on an existing install starts from the defaults, not from the install record. Options left off the command line change the install: leaving out --server host asks for a move back to a container, and a missing --proxy snippets switches to the managed Caddy. Anyone re-running install to change one thing, such as the names, has to repeat every option from the first run exactly.
Fix: on an existing install, take the shapes, proxy and dir from the record unless they're given on the command line. Have --dry-run say which values came from the record.
Split out of #81.
Running `install` again on an existing install starts from the defaults, not from the install record. Options left off the command line change the install: leaving out `--server host` asks for a move back to a container, and a missing `--proxy snippets` switches to the managed Caddy. Anyone re-running `install` to change one thing, such as the names, has to repeat every option from the first run exactly.
**Fix:** on an existing install, take the shapes, proxy and dir from the record unless they're given on the command line. Have `--dry-run` say which values came from the record.
jcoffey-dev
added this to the 27.1 milestone 2026-11-18 16:07:06 +00:00
Fixed in #85 (03c619d). Running install again now keeps every option it isn't given (shapes, proxy, names, ACME settings) and lists what it took in the plan. It also reloads Caddy when the Caddyfile changes; before this, new names weren't served until Caddy restarted. Tested in the lab with e2e/cases/rename.sh (#88).
Fixed in #85 (03c619d). Running `install` again now keeps every option it isn't given (shapes, proxy, names, ACME settings) and lists what it took in the plan. It also reloads Caddy when the Caddyfile changes; before this, new names weren't served until Caddy restarted. Tested in the lab with `e2e/cases/rename.sh` (#88).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Split out of #81.
Running
installagain on an existing install starts from the defaults, not from the install record. Options left off the command line change the install: leaving out--server hostasks for a move back to a container, and a missing--proxy snippetsswitches to the managed Caddy. Anyone re-runninginstallto change one thing, such as the names, has to repeat every option from the first run exactly.Fix: on an existing install, take the shapes, proxy and dir from the record unless they're given on the command line. Have
--dry-runsay which values came from the record.Fixed in #85 (
03c619d). Runninginstallagain now keeps every option it isn't given (shapes, proxy, names, ACME settings) and lists what it took in the plan. It also reloads Caddy when the Caddyfile changes; before this, new names weren't served until Caddy restarted. Tested in the lab withe2e/cases/rename.sh(#88).