Docker Compose¶
Best for a single host, a laptop, or a small team.
cp .env.example .env
$EDITOR .env
docker compose up -d
docker compose logs -f runtime
For a production host, add the overlay:
docker compose -f compose.yaml -f deploy/compose/compose.production.yaml up -d
It adds log rotation, a memory ceiling, and no-new-privileges.
Choose the variant¶
MULTICA_IMAGE=ghcr.io/proreka/multica-runtime:php
Autoscaler¶
The optional profile scales Swarm services, so it is only useful when the host is part of a swarm. On a plain compose host, run the runtime continuously.
docker compose --profile autoscaler up -d
It mounts the Docker socket. See Autoscaling.
State¶
The multica-workspaces volume holds sessions. Back it up before upgrades if you
care about claude --resume history; see Persistence.
Compose is not an orchestrator¶
restart: unless-stopped will start the container again after a crash, but there
is no rollout strategy and no placement constraint. If you need those, use
Swarm or ECS.