@rizom/ops
v0.2.0-alpha.108
Published
Operator CLI for managing private brain fleet registry repos
Downloads
7,145
Maintainers
Readme
brains-ops
Operator CLI package for managing pilot brain fleet registry repos.
Commands
brains-ops init <repo>brains-ops render <repo>— regeneratesviews/users.mdand fills status columns from built-in live probes (DNS,/health, unauthenticated/mcp)brains-ops user:add <repo> <handle> --cohort <cohort>— scaffolds a user file, per-user secrets template, and cohort membershipbrains-ops onboard <repo> <handle>— creates/seeds the user's content repo usingCONTENT_REPO_ADMIN_TOKENfor GitHub repo administration andGIT_SYNC_TOKENfor git clone/pushbrains-ops age-key:bootstrap <repo>brains-ops ssh-key:bootstrap <repo>brains-ops cert:bootstrap <repo>brains-ops secrets:push <repo>brains-ops secrets:encrypt <repo> <handle>brains-ops verify-user <repo> <handle>— checks/health, unauthenticated/mcp, and default-preset browser/CMS routesbrains-ops reconcile-cohort <repo> <cohort>brains-ops reconcile-all <repo>
Scope
brains-ops lives in the brains monorepo and is consumed as a separate package.
It operates on a separate private data repo, such as rover-pilot/, which stores:
pilot.yamlusers/*.yamlcohorts/*.yaml- generated
views/users.md - generated per-user config under
users/<handle>/brain.yaml - generated per-user env selectors under
users/<handle>/.env
