feat(web-ui): explicit copilot-web start + LAN bind by default on airgapped installs - #8
Merged
Merged
Conversation
…irgapped installs - `copilot-web` now requires an explicit subcommand: `start` or `stop`. Bare `copilot-web` (and the old `up`) print the usage line and exit 2. - Bind address resolution: COPILOT_UI_HOST env > ~/.copilot/ui-host file > loopback. setup-airgapped.sh writes 0.0.0.0 to ui-host on first install (operator override survives re-installs), so an airgapped console is reachable at http://<machine-ip>:3939 with no SSH tunnel. - Online installs (get.sh / setup.sh) keep the loopback-only default. - The start banner now prints the LAN URL when bound beyond loopback, and installers list `rantaiclaw setup login` before first console start. - Docs updated: README LAN section, QUICKSTART, installer next-steps.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
On an airgapped site the console binds loopback, so every operator needs
ssh -L 3939:127.0.0.1:3939just to open it. The LAN opt-in exists (COPILOT_UI_HOST=0.0.0.0) but must be retyped on every start. Separately, barecopilot-webdoubling as "start" reads ambiguously.Change
copilot-webnow requires an explicit subcommand:startorstop. Bare invocation (and the oldup) printusage: copilot-web start|stopand exit 2. Breaking for scripts that call the bare form; all shipped docs/installer messages updated.web-ui.sh:COPILOT_UI_HOSTenv →~/.copilot/ui-hostfile → loopback (rantaiclaw default).setup-airgapped.shwrites0.0.0.0to~/.copilot/ui-hostonly when the file doesn't exist, so an operator's override (echo 127.0.0.1 > ~/.copilot/ui-host) survives re-installs/updates. Airgapped console is then reachable athttp://<machine-ip>:3939with no tunnel.get.sh/setup.sh) keep loopback-only.rantaiclaw setup loginbefore first console start.Non-goals
ui startor gateway bind (gateway stays loopback; console proxies to it).Risk & rollback
echo 127.0.0.1 > ~/.copilot/ui-hostrestores loopback immediately without reinstalling.Validation
bash -non all touched scripts (shellcheck runs in CI).start/stop/bare/updispatch, LAN banner URL.0.0.0.0, re-install preserves operator's127.0.0.1, messages correct.tests/installer-matrix.sh61 passed,tests/bundle-consistency.sh23 passed (local rantaiclaw 0.18.3-alpha).