Running inbuxa install again over a server on the host rewrote server.env, the binary or the unit, but only restarted the server when the front ends changed shape or it was down. So the webmail-secret fix in 2026.10.12.4 needed a systemctl restart inbuxa-server by hand (its release notes say so).
Install and WriteUnit now say whether they changed anything, and converge restarts the server on that. With nothing changed it's left alone.
Tested in the lab VM:
new e2e/cases/rerun-host-server.sh (from v2026.10.12.3, server + webmail on the host): 12/12. Before: no secret, no sign-in. After the re-run: the secret is there, the server is a new process, sign-in works. A second re-run leaves the same process running.
Running `inbuxa install` again over a server on the host rewrote `server.env`, the binary or the unit, but only restarted the server when the front ends changed shape or it was down. So the webmail-secret fix in 2026.10.12.4 needed a `systemctl restart inbuxa-server` by hand (its release notes say so).
`Install` and `WriteUnit` now say whether they changed anything, and converge restarts the server on that. With nothing changed it's left alone.
Tested in the lab VM:
- new `e2e/cases/rerun-host-server.sh` (from v2026.10.12.3, server + webmail on the host): 12/12. Before: no secret, no sign-in. After the re-run: the secret is there, the server is a new process, sign-in works. A second re-run leaves the same process running.
- `all-host.sh`: 18/18
- `upgrade-host-server.sh` (from v2026.10.12.1): 11/11
- `go vet` and `go test ./...` are clean
Running install again rewrote server.env, the binary or the unit but only
restarted the server when the front ends changed shape or it was down, so
a fix to its environment (the webmail's secret, 2026.10.12.4) waited for a
restart by hand. Install and WriteUnit now say whether they changed
anything, and converge restarts on that; with nothing changed the server is
left alone.
e2e/cases/rerun-host-server.sh starts from v2026.10.12.3 and checks both.
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.
Running
inbuxa installagain over a server on the host rewroteserver.env, the binary or the unit, but only restarted the server when the front ends changed shape or it was down. So the webmail-secret fix in 2026.10.12.4 needed asystemctl restart inbuxa-serverby hand (its release notes say so).InstallandWriteUnitnow say whether they changed anything, and converge restarts the server on that. With nothing changed it's left alone.Tested in the lab VM:
e2e/cases/rerun-host-server.sh(from v2026.10.12.3, server + webmail on the host): 12/12. Before: no secret, no sign-in. After the re-run: the secret is there, the server is a new process, sign-in works. A second re-run leaves the same process running.all-host.sh: 18/18upgrade-host-server.sh(from v2026.10.12.1): 11/11go vetandgo test ./...are clean