A team of long-lived bots for DeepSeek Harness, with main bots, bot-to-bot messages and group chats.
Publish tested Docker images to GHCR
klarkxya2ad0cfbb346
diff --git a/.github/workflows/test.yml b/.github/workflows/test.ymlindex d2a544d0..0581cce1 100644--- a/.github/workflows/test.yml+++ b/.github/workflows/test.yml@@ -58,6 +58,10 @@ jobs:name: Docker startup and data migrationruns-on: ubuntu-latesttimeout-minutes: 20+ needs: [test, scan]+ permissions:+ contents: read+ packages: writesteps:- uses: actions/checkout@v4- uses: actions/setup-node@v4@@ -67,6 +71,27 @@ jobs:- run: docker compose -f docker/compose.yml config --quiet- run: docker build -f docker/Dockerfile -t ds-bot:test .- run: node docker/test.mjs ds-bot:test+ - name: Publish the tested image+ if: github.event_name == 'push' && github.repository == 'Fei2411/DeepSeek-Bot'+ env:+ GHCR_TOKEN: ${{ secrets.GITHUB_TOKEN }}+ GHCR_ACTOR: ${{ github.actor }}+ GHCR_REPOSITORY: ${{ github.repository }}+ GHCR_BRANCH: ${{ github.ref_name }}+ GHCR_SHA: ${{ github.sha }}+ run: |+ set -euo pipefail+ image="ghcr.io/${GHCR_REPOSITORY,,}"+ case "$GHCR_BRANCH" in+ main) tag=latest ;;+ dev) tag=dev ;;+ *) exit 0 ;;+ esac+ printf '%s' "$GHCR_TOKEN" | docker login ghcr.io -u "$GHCR_ACTOR" --password-stdin+ docker tag ds-bot:test "$image:sha-$GHCR_SHA"+ docker tag ds-bot:test "$image:$tag"+ docker push "$image:sha-$GHCR_SHA"+ docker push "$image:$tag"# The one check that branch rules require. A job whose needs failed is skipped,# and GitHub counts a skipped required check as passed, so this job always runsdiff --git a/README.md b/README.mdindex a121cf85..076c7cb5 100644--- a/README.md+++ b/README.md@@ -38,7 +38,7 @@ npx @deepseek-ai/[email protected] web**Docker (NAS, Linux server)**-The [`docker/`](docker/) directory builds an image with DSH Web and DS Bot, for a NAS or any always-on machine. The container is the Bots' sandbox: they get full access to what you mount into it, and nothing else. See [`docker/README.md`](docker/README.md).+The [`docker/`](docker/) directory builds an image with DSH Web and DS Bot, for a NAS or any always-on machine. CI is configured to publish a prebuilt linux/amd64 image to GHCR. The container is the Bots' sandbox: they get full access to what you mount into it, and nothing else. See [`docker/README.md`](docker/README.md).## Setupdiff --git a/README.zh.md b/README.zh.mdindex 95fc2ac1..ade9749f 100644--- a/README.zh.md+++ b/README.zh.md@@ -38,7 +38,7 @@ npx @deepseek-ai/[email protected] web**Docker(NAS、Linux 服务器)**-[`docker/`](docker/) 目录构建一个带 dsh Web 和 DS Bot 的镜像,适合 NAS 或其他常开的机器。容器就是 bot 的沙箱:bot 对挂进容器的目录有完全权限,其他的碰不到。见 [`docker/README.md`](docker/README.md)(英文)。+[`docker/`](docker/) 目录构建一个带 dsh Web 和 DS Bot 的镜像,适合 NAS 或其他常开的机器。CI 已配置为向 GHCR 发布 linux/amd64 预构建镜像。容器就是 bot 的沙箱:bot 对挂进容器的目录有完全权限,其他的碰不到。见 [`docker/README.md`](docker/README.md)(英文)。## 配置diff --git a/docker/README.md b/docker/README.mdindex 52653794..31a731a2 100644--- a/docker/README.md+++ b/docker/README.md@@ -169,6 +169,48 @@ image is built and tested with dsh `0.2.0-rc.2`, the versionDS Bot is verified with; a `DSH_VERSION` build arg exists, but other releasesare untested and newer ones change how the server binds.+## Prebuilt image++GitHub Actions publishes the image to GHCR after the branch CI succeeds:+`main` as `latest`, `dev` as `dev`, and every successful push also as+`sha-<full commit SHA>`. Only the tested linux/amd64 image is published. The+first publication happens only after this workflow is merged and a push+succeeds. The maintainer must set the GHCR package visibility to Public once+before anonymous pulls work.++Save this as `compose.yml` in the directory you want to deploy from. Fill in+the API key and your NAS host names before starting it. Running these commands+from the repository root would use the local root Compose file instead.++```yaml+services:+ ds-bot:+ image: ghcr.io/fei2411/deepseek-bot:dev+ ports:+ - "13080:3080"+ environment:+ DEEPSEEK_API_KEY: ""+ PUID: "1000"+ PGID: "1000"+ DSH_TRUSTED_HOST: "localhost,127.0.0.1"+ volumes:+ - ./data:/data+ - ./workspace:/workspace+ extra_hosts:+ - "host.docker.internal:host-gateway"+ restart: unless-stopped+ stop_grace_period: 15s+```++```sh+docker compose pull+docker compose up -d+```++The root `docker-compose.yml` and `docker/compose.yml` still build the local+image. Choose one setup; do not run both against the same data directory. An+existing persisted profile is not upgraded automatically.+## Limits- No Bot browser / `read_browser` tool: those exist in dsh Desktop only.