inbuxa with no arguments, or inbuxa install with no options, now opens the installer spec's interface (§4). It has six screens, always in this order:
What it found: the survey text, now shared with inbuxa survey via plan.SurveyText.
Names: mail domain, server, console and webmail names, ACME contact, directory, and a "try it on loopback" toggle. Defaults show as placeholders, and loopback fills in example.test.
Components: skip / container / host for each component.
What the machine can't do is greyed out, with the reason.
What it lacks but the installer can add (docker, compose) is offered and added, with --install-deps in the command.
Defaults match the flags. Front ends without a server here point you to join.
Reach: Caddy, or your own web server. On loopback there's nothing to choose.
The plan:plan.Build's plan in full, scrollable, plus the command that does the same without the interface. Enter asks "Install now? … y", and nothing happens before that. Without root it refuses with the reason.
Install:apply.Run's steps ticking off, with output underneath. Stopping a running install asks first. It ends on the credentials and addresses, which are printed again once the terminal is restored, so they stay in the scrollback.
It fills in the same plan.Options the flags do, so it's a way of choosing, not a second installer. Without a terminal it says which flags to use (exit 2), and a window under 60x16 says so.
Terminal layer: our own, on the standard library only (spec §8, decision 1). Raw mode, window size and SIGWINCH go through syscall, with a stub so it still compiles off Linux. It also decodes keys, redraws the whole frame each time, honors NO_COLOR, and restores the terminal on every way out, including a panic.
Also in this PR
plan.Available now says host installs of the console and webmail aren't built, so --console host is refused when the plan is built instead of failing partway through the install.
Found while building this:--proxy snippets is in the plan, the usage text and the docs, but apply never writes those files. The interface leaves it out, and the README now says so. Fixing it is a separate, small PR.
Tests
Key decoding, fitting and wrapping.
The wizard driven by keys against a fake installer, under -race: defaults, loopback, the server on the host, refusals (a console host install, a missing server, a bad name, not root), confirming with y, stopping a running install, a machine without docker, a small window.
e2e/cases/interface.sh (22/22): drives the real binary in a pseudo-terminal on a fresh Debian 13 lab, through a whole loopback install including docker. It also checks that nothing is written before the y, that the terminal is restored, that the summary is left in it, that status agrees, and the no-terminal path.
install-local, install-host, install-public, status-export and topology pass unchanged. join wasn't re-run: it needs a server build, and nothing it uses changed.
Not in this PR:join from the interface (it's a command for now), and the docs page.
`inbuxa` with no arguments, or `inbuxa install` with no options, now opens the installer spec's interface (§4). It has six screens, always in this order:
1. **What it found:** the survey text, now shared with `inbuxa survey` via `plan.SurveyText`.
2. **Names:** mail domain, server, console and webmail names, ACME contact, directory, and a "try it on loopback" toggle. Defaults show as placeholders, and loopback fills in `example.test`.
3. **Components:** skip / container / host for each component.
- What the machine can't do is greyed out, with the reason.
- What it lacks but the installer can add (docker, compose) is offered and added, with `--install-deps` in the command.
- Defaults match the flags. Front ends without a server here point you to `join`.
4. **Reach:** Caddy, or your own web server. On loopback there's nothing to choose.
5. **The plan:** `plan.Build`'s plan in full, scrollable, plus **the command that does the same without the interface**. Enter asks **"Install now? … y"**, and nothing happens before that. Without root it refuses with the reason.
6. **Install:** `apply.Run`'s steps ticking off, with output underneath. Stopping a running install asks first. It ends on the credentials and addresses, which are printed again once the terminal is restored, so they stay in the scrollback.
It fills in the same `plan.Options` the flags do, so it's a way of choosing, not a second installer. Without a terminal it says which flags to use (exit 2), and a window under 60x16 says so.
**Terminal layer:** our own, on the standard library only (spec §8, decision 1). Raw mode, window size and SIGWINCH go through `syscall`, with a stub so it still compiles off Linux. It also decodes keys, redraws the whole frame each time, honors `NO_COLOR`, and restores the terminal on every way out, including a panic.
**Also in this PR**
- `plan.Available` now says host installs of the console and webmail aren't built, so `--console host` is refused when the plan is built instead of failing partway through the install.
- **Found while building this:** `--proxy snippets` is in the plan, the usage text and the docs, but apply never writes those files. The interface leaves it out, and the README now says so. Fixing it is a separate, small PR.
**Tests**
- Key decoding, fitting and wrapping.
- The wizard driven by keys against a fake installer, under `-race`: defaults, loopback, the server on the host, refusals (a console host install, a missing server, a bad name, not root), confirming with y, stopping a running install, a machine without docker, a small window.
- **`e2e/cases/interface.sh` (22/22):** drives the real binary in a pseudo-terminal on a fresh Debian 13 lab, through a whole loopback install including docker. It also checks that nothing is written before the y, that the terminal is restored, that the summary is left in it, that `status` agrees, and the no-terminal path.
- install-local, install-host, install-public, status-export and topology pass unchanged. `join` wasn't re-run: it needs a server build, and nothing it uses changed.
**Not in this PR:** `join` from the interface (it's a command for now), and the docs page.
`inbuxa` with no arguments (or `inbuxa install` with no options) opens the
installer spec's interface in the terminal: what it found on this machine,
the names, which components go here and how, what answers on 80 and 443,
the whole plan, and the install. It fills in the same plan.Options the
flags do, builds the plan with plan.Build and installs with apply.Run: it
is a way of choosing, not a second installer. The plan screen shows the
command that does the same without it, and nothing happens until a "y".
- Components: what the machine can't do is greyed out with the reason
beside it; what it lacks and the installer can add (docker, compose) is
offered and added, with --install-deps in the command. The defaults are
the flags' defaults. Front ends without a server here point to join.
- Reach offers Caddy or your own web server. --proxy snippets is left out:
the plan describes it, but nothing writes those files yet (now said in
the README).
- The install screen ticks off apply's steps with its output underneath,
asks before stopping a running install, and ends on the credentials and
addresses, printed again once the terminal is given back.
- Without root it refuses at the plan, saying why. Without a terminal it
says which flags do the same, exit 2. A window under 60x16 says so.
The terminal layer is ours and the standard library's (installer spec §8,
decision 1): raw mode, size and SIGWINCH through syscall, key decoding,
full redraws, NO_COLOR honored, the terminal restored on every way out.
Also: the survey's text moved to plan.SurveyText, which the first screen
and `inbuxa survey` share; and plan.Available now says host installs of the
console and the webmail aren't built, so --console host is refused at the
plan instead of after it.
Tests: key decoding, fitting and wrapping, and the wizard driven by keys
against an installer that changes nothing (defaults, loopback, the server
on the host, refusals, root and the y, stopping, a machine without docker,
a small window), under -race. e2e/cases/interface.sh drives the binary in a
pseudo-terminal on a fresh Debian 13 lab through a whole loopback install:
22/22. install-local, install-host, install-public, status-export and
topology pass unchanged.
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.
inbuxawith no arguments, orinbuxa installwith no options, now opens the installer spec's interface (§4). It has six screens, always in this order:inbuxa surveyviaplan.SurveyText.example.test.--install-depsin the command.join.plan.Build's plan in full, scrollable, plus the command that does the same without the interface. Enter asks "Install now? … y", and nothing happens before that. Without root it refuses with the reason.apply.Run's steps ticking off, with output underneath. Stopping a running install asks first. It ends on the credentials and addresses, which are printed again once the terminal is restored, so they stay in the scrollback.It fills in the same
plan.Optionsthe flags do, so it's a way of choosing, not a second installer. Without a terminal it says which flags to use (exit 2), and a window under 60x16 says so.Terminal layer: our own, on the standard library only (spec §8, decision 1). Raw mode, window size and SIGWINCH go through
syscall, with a stub so it still compiles off Linux. It also decodes keys, redraws the whole frame each time, honorsNO_COLOR, and restores the terminal on every way out, including a panic.Also in this PR
plan.Availablenow says host installs of the console and webmail aren't built, so--console hostis refused when the plan is built instead of failing partway through the install.--proxy snippetsis in the plan, the usage text and the docs, but apply never writes those files. The interface leaves it out, and the README now says so. Fixing it is a separate, small PR.Tests
-race: defaults, loopback, the server on the host, refusals (a console host install, a missing server, a bad name, not root), confirming with y, stopping a running install, a machine without docker, a small window.e2e/cases/interface.sh(22/22): drives the real binary in a pseudo-terminal on a fresh Debian 13 lab, through a whole loopback install including docker. It also checks that nothing is written before the y, that the terminal is restored, that the summary is left in it, thatstatusagrees, and the no-terminal path.joinwasn't re-run: it needs a server build, and nothing it uses changed.Not in this PR:
joinfrom the interface (it's a command for now), and the docs page.