Module: VIBE

Deployment code-server package not found Ensure NODE and repo config are in place: yum repolist # EL apt-cache policy # Debian/Ubuntu, read-only inspection ./infra.yml -l infra -t repo --check JupyterLab installation failed jupyter_venv must exist: …

VIBE monitoring mainly focuses on Claude Code OpenTelemetry data. Code-Server and JupyterLab do not expose Prometheus metrics; use systemd and logs for health checks. Claude Code Observability VIBE writes default OpenTelemetry env vars into …

Service Management systemctl status code-server systemctl restart code-server systemctl status jupyter systemctl restart jupyter Logs: journalctl -u code-server -f journalctl -u jupyter -f Workspace and Context vibe_dir creates these under …

VIBE provides the vibe.yml playbook to deploy Code-Server, JupyterLab, Node.js, Claude Code, and Codex CLI. vibe.yml includes only node_id and vibe roles, it does not include node/infra. Run deploy.yml first, or explicitly run node.yml and infra.yml. …

VIBE module has 18 parameters, grouped as: Common Code-Server JupyterLab Node.js Claude Code Codex CLI Overview Parameter Type Level Default Description vibe_data path C /fs Workspace dir code_enabled bool C true Enable Code-Server code_port port C …

VIBE supports enabling components on demand and exposes services via a unified workspace and Nginx portal. Overview Component Enable Param Default Description Code-Server code_enabled Enabled VS Code in browser JupyterLab jupyter_enabled Disabled …

The VIBE module provides a browser-based dev environment with Code-Server, JupyterLab, Node.js, Claude Code, and Codex CLI, and can work with JUICE shared storage and PGSQL database capabilities. VIBE depends on NODE and INFRA: NODE provides base …