Deploy DS Bot on a NAS or always-on host with Docker

Official docker/README Quick start: root compose local build, host port 13080

Who

Operators who want DS Bot (DSH Web + plugin) always on a NAS or Linux server

You get

Container running; first browser visit with the log token sets the cookie; Chief is created on first team open

You need

DS Bot · DeepSeek Harness · Docker

Steps

1. Prepare

   Requirements: Docker 24+ with Compose v2.24+; linux/amd64 containers (arm64 untested upstream); a DeepSeek API key (or another Anthropic-Messages-compatible endpoint via DEEPSEEK_BASE_URL).

2. Edit compose

   From the repository root, edit `docker-compose.yml`: set `DEEPSEEK_API_KEY`, add the NAS IP to `DSH_TRUSTED_HOST` (no port), and set `PUID`/`PGID` to the share owner. Env, ports, and paths live in this file — no `.env` required. Do not commit real keys.

3. Build & logs

   Run `docker compose up -d --build`, then `docker compose logs ds-bot` and copy the token login URL. The root Compose file publishes host port **13080** and stores data under `docker/data` and `docker/workspace`.

   Setup guidance · Source text。Give to a setup assistant; not a node execution prompt.

   Copy prompt

   docker compose up -d --build
   docker compose logs ds-bot

4. Browser login

   Open `http://<NAS IP>:13080/?token=…` once so the signed cookie is set (~30 days, bound to that authority); afterward use `http://<NAS IP>:13080/`. The first team open creates Main Bot Chief. The alternative `docker/` `.env`+compose defaults to host port 3080 — pick one method and do not share the same data directory. Over plain HTTP, secrets cross the LAN in clear text; the docs recommend HTTPS/a reverse proxy for regular use.

This case is Docker/NAS deploy guidance. There is no official pasteable end-user task prompt. Follow the Quick start steps to edit compose, build, and log in with the token from the logs; copyable official commands are in the step prompt blocks.