Vibecape Server

Vibecape Server manages Groups, membership, Spaces, Git repositories, and synchronization authorization. A server instance binds to one Downcity Federation.

Initialize and run

vibecape server init
vibecape server start
vibecape server status

Initialization writes ~/.vibecape/server.env with permission 0600 and asks for the Federation URL, Bureau Token, City ID, listen address, public URL, and data directory. The Bureau Token is not echoed.

server start launches a background process and returns the terminal after its health check passes. Runtime files are stored in the configured data directory:

• server.pid records the managed process;
• server.log contains background logs;
• the SQLite database stores Groups, members, Spaces, and audit data;
• bare repositories store Space content and history.

vibecape server restart
vibecape server stop
vibecape server start --foreground

Use start --foreground only for foreground debugging or when systemd, Docker, or Dokploy owns the process lifecycle. Plain start lets Vibecape manage its own background process.

Group administration

vibecape server group create --name "Research Team"
vibecape server group list
vibecape server group member list <group-id>
vibecape server group member add <group-id> <user-id> --role editor
vibecape server group transfer-owner <group-id> <user-id>

Back up the configured data directory as one unit. The database and bare repositories must remain consistent.