packaging(cockpit): install the sovereign cockpit as brew CLIs (OBJ-A last mile)#74
Merged
Merged
Conversation
OBJ-A last mile — the assembled cockpit now installs + runs as one product, not just
from a staging dir.
- Homebrew formula: two CLIs alongside the existing sidecar wrappers —
bearbrowser-cockpit-assemble → assemble-cockpit.sh (build client-vue + sidecar)
bearbrowser-cockpit-up → the governed orchestrator
Both target a WRITABLE user data dir (${XDG_DATA_HOME:-~/.local/share}/bearbrowser/
cockpit-app/…) because the Cellar is read-only — assemble can't build into libexec.
Kept LEAN: no node/bun added as hard deps on the whole browser; assemble checks +
guides (caveat notes 'brew install node bun'). Caveats + a fast test added.
- bearbrowser-cockpit-up: honor BEARBROWSER_COCKPIT_RES so the installed CLI finds the
user-dir app (dev/staging still auto-derives from the script's parent).
Verified: ruby -c OK; cockpit-up errors cleanly + exit 1 before assembly (the test);
BEARBROWSER_COCKPIT_RES override resolves the staged app and stands up the governed
topology (cockpit→gate→sidecar + receipts). Full brew install cycle for you to run:
brew install --formula packaging/homebrew/Formula/bearbrowser.rb # runs the test
brew install node bun && bearbrowser-cockpit-assemble && bearbrowser-cockpit-up
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
1 participant
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.
The last mile of OBJ-A: the assembled cockpit now installs and runs as one product, not just from a staging dir.
What lands:
bearbrowser-cockpit-assemble→ builds client-vue + the agent-machine sidecar binarybearbrowser-cockpit-up→ the governed orchestrator (cockpit → gate → sidecar + receipts)${XDG_DATA_HOME:-~/.local/share}/bearbrowser/cockpit-app/…) — the Cellar is read-only, so assemble can't build intolibexec.bearbrowser-cockpit-uphonorsBEARBROWSER_COCKPIT_RESso the installed CLI finds the user-dir app (dev/staging still auto-derives).node/bunhard deps on the whole browser — assemble checks and guides; a caveat notesbrew install node bun. Caveats + a fast test added.Verified:
ruby -cOK ·cockpit-uperrors cleanly (exit 1) before assembly (the test) · theBEARBROWSER_COCKPIT_RESoverride resolves the staged app and stands up the governed topology.For you to run the full cycle:
With this, OBJ-A is complete: assemble → install → run, governed, sovereign.