Tide Commander includes a multi-stage Dockerfile for containerized deployment.
docker build -t tide-commander .
docker run -p 5174:5174 \
-v ~/.local/share/tide-commander:/root/.local/share/tide-commander \
tide-commander
docker run -p 5174:5174 \
-e AUTH_TOKEN=your-secret-token \
-v ~/.local/share/tide-commander:/root/.local/share/tide-commander \
tide-commander
docker run -p 5174:5174 \
-e LISTEN_ALL_INTERFACES=1 \
-v ~/.local/share/tide-commander:/root/.local/share/tide-commander \
tide-commander
- The container needs
claude CLI accessible inside for agent processes to work. You may need to mount the Claude binary and its dependencies, or install it in the image.
- Custom 3D models are stored in
~/.tide-commander/custom-models/ - mount this volume if you use custom models.
- The production build serves the frontend from the same port (5174) as the API.
| Variable |
Default |
Description |
PORT |
5174 |
Server port |
NODE_ENV |
production |
Set by the Dockerfile |
LISTEN_ALL_INTERFACES |
(unset) |
Set to 1 to listen on 0.0.0.0 |
AUTH_TOKEN |
(unset) |
Token for authentication |
| Path |
Purpose |
/root/.local/share/tide-commander |
Agent state, buildings, skills, snapshots, secrets |
/root/.tide-commander/custom-models |
Custom 3D model files (if used) |