clawdie/colibri
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 25
colibri/docs/guide/install/controlplane-install.md
Sam & Claude 79f67bf575
Some checks are pending
CI / rust (pull_request) Waiting to run
Details
CI / markdown (pull_request) Waiting to run
Details
CI / port (pull_request) Waiting to run
Details
CI / agent-jail-pkgs (pull_request) Waiting to run
Details
docs(guide): correct install docs to clawdie binary (not just/Ansible) 
Replace legacy just install / just setup-* references with
clawdie binary commands (clawdie plan, clawdie apply --yes).
Document scope: what the installer does not do (yet).
Trim the clawdie-ai just orchestrator step tables.

Rebased from #213 onto current main; supersedes #217.
2026-06-26 15:00:34 +02:00

926 B
Raw Permalink Blame History

title description
Control Plane Install Install the Clawdie control-plane host service with the clawdie binary.

The control plane runs as the host-managed clawdie service (colibri-daemon), provisioned by the clawdie binary:

cargo build -p clawdie --release
clawdie apply --yes

This installs the storage datasets, the clawdie service user, and the rc.d (FreeBSD) / systemd (Linux) unit that runs colibri-daemon. Preview first with clawdie plan; apply is a dry-run until you pass --yes. See Install for the full command set, storage strategy, and safety notes.

Scope. This provisions the control-plane host service only. PF egress, worker jails, PostgreSQL, and the CMS/web service were handled by the legacy clawdie-ai just + Ansible orchestrator and are not yet part of the colibri installer. The canonical Bastille/Warden bridge name remains warden0.