Bootstrap and verify self-hosted Rakazo from published images
Prepare a Docker-based Rakazo installation, preserve private configuration, and verify service health, the selected sandbox, and an optional first bot reply before handoff.
npx skills add agentskillexchange/skills --skill bootstrap-and-verify-self-hosted-rakazo-from-published-images
Invoke this workflow when you want a coding agent to bring up a self-hosted Rakazo instance from published images and return evidence that its services and selected agent computer work. It follows the upstream agent-assisted setup procedure, with a bounded handoff from host preflight to verified local installation.
What this skill actually does
Choose the setup boundary
Agree on an installation directory, the intended ordinary account, and whether to connect a model during onboarding or defer it. Use local Docker computers by default; configure a remote provider only when the operator selects one and supplies its credential privately. This workflow covers the published-image web stack. Keep source development, public-server deployment, fleet orchestration, and unrelated application integrations outside this run.
Preflight and prepare
Check Docker Engine, its Compose plugin, curl, OpenSSL, the running daemon, and loopback port availability. Identify conflicts without stopping unrelated workloads. Read the upstream setup procedure and self-hosting guide. Download and inspect the installer before execution. A pinned installer still downloads configuration from main unless RAKAZO_DOWNLOAD_BASE is explicitly set to the reviewed revision’s infra/compose directory; image tags remain a separate choice.
curl -fsSL https://raw.githubusercontent.com/elie222/rakazo/f9165321526c4923816c5e854c16ff078059bd07/infra/compose/install-images.sh -o install-images.sh
# Review the downloaded script before running it.
export RAKAZO_DOWNLOAD_BASE=https://raw.githubusercontent.com/elie222/rakazo/f9165321526c4923816c5e854c16ff078059bd07/infra/compose
bash install-images.sh --prepare-onlyPreserve existing environment values and inspect key presence without printing secrets. The installer creates a private environment file with random secrets on a fresh installation and can append a missing application database password to an existing file. Review that behavior before rerunning against an existing deployment. Apply only agreed provider/model settings; leave account sign-in and credentials under the operator’s control. Without email delivery, keep public signup disabled and use the documented private bootstrap-owner procedure for the intended ordinary account. Signup order grants no server privileges.
Start and verify
Run bash install-images.sh after preparation and configuration review. The installer may install host firewall rules for restricted computer egress or record open egress when restrictions are unavailable. Review that host change and effective egress choice with the operator; do not silently treat open egress as isolated networking. Wait for the API, web, and sandbox supervisor to become healthy. The documented default image tag is edge; do not assume latest exists. Record the effective image versions or digests.
Inspect the internal API health response using the documented local or in-container route. Require ok=true and the selected sandbox provider. A response with sandbox=none does not pass a Docker setup. Open the loopback web UI at http://127.0.0.1:5173, let the operator complete account/model onboarding, and check that the selected agent computer reaches running and displays its desktop. With a model connected, send a harmless test message and verify a reply. If model setup is deferred, report infrastructure-only success and leave message verification pending.
Return a reviewable handoff
Report the directory, Docker/Compose versions, effective image identity, configured provider names without credentials, app URL, service health, computer readiness, message result, and unresolved blockers. Explain how to stop with the appropriate Compose files and down without -v; retain volumes and private configuration. Do not claim success from a running container or downloaded installer alone.
This is a reusable setup-and-verification procedure for coding agents with shell access and optional browser assistance. It is not an MCP server invocation or a listing of Rakazo’s general assistant features. Metadata and upstream instructions were checked; no installation, runtime evaluation, or security review was performed during discovery.