Upload 4 files

Dockerfile

@@ -0,0 +1,63 @@
+# syntax=docker/dockerfile:1
+#
+# DeepSeek Harness (dsh) on a Hugging Face Docker Space.
+#
+# Persistent user data:
+#   Hugging Face Storage Bucket -> /home/user
+#
+# DSH itself and nginx live in the image; DSH's user data, settings, credentials,
+# sessions, plugins, auth state, and user-level caches live under /home/user.
+
+FROM node:24-bookworm-slim
+
+# Always build the current DSH release.
+ARG DSH_VERSION=latest
+ARG MOBILE_CSS_PLUGIN="dsh-mobile-css@latest"
+ARG REMOTE_AUTH_PLUGIN="dsh-web-startup-auth@latest"
+
+ENV HOME=/home/user
+ENV DSH_HOME=/home/user/.dsh
+
+# Keep user-level configuration/cache/package-manager state inside the persistent bucket.
+ENV XDG_CONFIG_HOME=/home/user/.config
+ENV XDG_DATA_HOME=/home/user/.local/share
+ENV XDG_STATE_HOME=/home/user/.local/state
+ENV XDG_CACHE_HOME=/home/user/.cache
+ENV NPM_CONFIG_CACHE=/home/user/.cache/npm
+ENV PNPM_HOME=/home/user/.local/share/pnpm
+
+ENV MOBILE_CSS_PLUGIN=${MOBILE_CSS_PLUGIN}
+ENV REMOTE_AUTH_PLUGIN=${REMOTE_AUTH_PLUGIN}
+
+# DSH requires Node >=22.19 or >=24; Node 24 is the current LTS line.
+RUN apt-get update && apt-get install -y --no-install-recommends \
+        nginx-light \
+        curl \
+        ca-certificates \
+    && rm -rf /var/lib/apt/lists/*
+
+# Install DSH globally outside /home/user so the image contains the runtime.
+ENV NPM_CONFIG_PREFIX=/opt/npm-global
+ENV PATH=/opt/npm-global/bin:/home/user/.local/share/pnpm:$PATH
+# DSH's plugin manager is a thin wrapper around pnpm, so pnpm must be
+# available on PATH at runtime. Install both globally in the image; the
+# actual DSH profile/plugin state remains under the persistent /home/user.
+RUN npm install -g pnpm@latest @deepseek-ai/dsh@${DSH_VERSION}
+
+# Hugging Face Docker Spaces convention: uid 1000, home = /home/user.
+RUN if getent passwd 1000 >/dev/null; then userdel -r "$(getent passwd 1000 | cut -d: -f1)"; fi \
+    && useradd -m -u 1000 user
+
+WORKDIR /app
+
+COPY --chown=user:user nginx.conf /etc/nginx/nginx.conf
+RUN mkdir -p /var/lib/nginx /var/log/nginx \
+    && chown -R user:user /var/lib/nginx /var/log/nginx /etc/nginx
+
+COPY --chown=user:user entrypoint.sh /app/entrypoint.sh
+RUN chmod +x /app/entrypoint.sh
+
+USER user
+
+EXPOSE 7860
+CMD ["/app/entrypoint.sh"]

README.md

@@ -0,0 +1,112 @@
+---
+title: DeepSeek Harness
+emoji: 🐳
+colorFrom: blue
+colorTo: gray
+sdk: docker
+app_port: 7860
+---
+
+# DeepSeek Harness (dsh) on a Hugging Face Space
+
+This Space runs the latest DeepSeek Harness behind nginx with persistent Hugging
+Face Storage and the `dsh-web-startup-auth` remote-access/auth plugin.
+
+## Storage: persist the whole user home
+
+Attach a Hugging Face Storage Bucket to this Space and mount it at:
+
+`/home/user`
+
+Use read-write access.
+
+This persists the entire user home, including:
+
+- `$DSH_HOME` (`/home/user/.dsh`)
+- DSH settings and provider configuration
+- DSH credentials stored by the app
+- sessions and workspace/user data
+- installed DSH profile plugins
+- web-auth state (`web-auth.json`)
+- user-level `.config`, `.local`, and `.cache` data
+
+System software installed into the Docker image (`/usr`, `/opt/npm-global`,
+nginx, Node, and the DSH runtime itself) remains part of the image and is
+recreated from the Dockerfile on rebuild. That is intentional.
+
+## Remote settings / Models fix
+
+The stock DSH web startup keeps remote privileged configuration APIs loopback-only,
+and the browser also disables settings on a non-loopback hostname. The current
+deployment therefore installs `dsh-web-startup-auth@latest` into the web profile.
+
+That plugin provides authenticated remote browser access, fixes the remote
+browser settings gate, handles privileged loopback-authority APIs after
+authentication, and supplies the browser crypto compatibility needed by remote
+HTTP contexts.
+
+The plugin is installed/updated from the npm `latest` tag at every container
+start. If the registry is temporarily unavailable, an already-installed copy is
+kept; a first boot fails rather than silently starting without the security and
+settings layer.
+
+See the plugin's current documentation for the authentication flow. On first
+visit, use its registration/login page to create the administrator account.
+The authentication state is stored under `/home/user/.dsh`, so it survives
+restarts when the bucket is attached.
+
+## Latest packages
+
+The Docker build installs:
+
+- `@deepseek-ai/dsh@latest`
+- `dsh-mobile-css@latest`
+- `dsh-web-startup-auth@latest`
+
+The two web plugins are also refreshed on every boot so a persistent profile
+doesn't permanently pin an old plugin version.
+
+## Hugging Face visibility
+
+Keep this Space **Private**. DSH has powerful filesystem/agent capabilities.
+The authentication plugin is an additional application-level security layer,
+not a reason to make a powerful agent public.
+
+## Secrets
+
+Put API keys in Hugging Face Space **Settings → Secrets**, not in this repo.
+
+## Port
+
+Hugging Face routes the Space to port `7860`. nginx listens on `7860` and
+proxies to DSH on `0.0.0.0:3080` inside the container.
+
+## Why nginx no longer rewrites Host/Origin
+
+The earlier configuration rewrote `Host`/`Origin` to localhost. That could make
+the server-side loopback check pass, but it could not change the browser's
+actual `location.hostname`, which is what caused:
+
+`settings are unavailable in this browser`
+
+The remote-auth plugin is designed to solve both sides: the browser-side remote
+settings gate and the authenticated server-side privileged API boundary. nginx
+therefore preserves the HF authority and forwards the real request metadata.
+
+
+## Plugin package manager
+
+`dsh plugin --profile web ...` forwards plugin operations to pnpm. The image
+therefore installs **pnpm@latest** globally as well as **@deepseek-ai/dsh@latest**.
+The pnpm executable is outside `/home/user`; the profile, lockfile, installed
+plugins, settings, auth state, credentials, sessions, and user-level caches are
+inside `/home/user` and are persisted by the HF Storage Bucket.
+
+On every container start the entrypoint runs:
+
+- `dsh plugin --profile web add dsh-mobile-css@latest`
+- `dsh plugin --profile web add dsh-web-startup-auth@latest`
+
+A successful run updates the persistent profile to the current npm `latest`
+versions. If npm is temporarily unreachable, an already-installed plugin is
+kept so the Space can still start.

entrypoint.sh

@@ -0,0 +1,55 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+# The HF Storage Bucket is mounted at /home/user. Keep all user-level state
+# underneath it so DSH settings, credentials, sessions, plugins, auth state,
+# and package-manager caches survive container restarts/rebuilds.
+mkdir -p \
+  "$HOME/.dsh" \
+  "$HOME/.config" \
+  "$HOME/.local/share" \
+  "$HOME/.local/state" \
+  "$HOME/.cache/npm" \
+  "$HOME/.cache"
+
+# dsh plugin is a pnpm forwarder. pnpm is installed globally in the image.
+# Install/update both runtime UI plugins from the npm latest tag on every boot.
+# If the registry is temporarily unavailable but an existing copy is present,
+# keep the existing copy; otherwise fail rather than silently starting without
+# the remote-settings/auth capability.
+ensure_latest_plugin() {
+    local spec="$1"
+    local package_name="$2"
+
+    echo "[entrypoint] installing/updating ${spec}"
+    if dsh plugin --profile web add "${spec}"; then
+        echo "[entrypoint] ${package_name}: latest install/update succeeded"
+        return 0
+    fi
+
+    if [ -d "$DSH_HOME/profiles/web/node_modules/$package_name" ]; then
+        echo "[entrypoint] ${package_name}: registry update failed; keeping existing installed copy"
+        return 0
+    fi
+
+    echo "[entrypoint] ERROR: ${package_name} is not installed and could not be fetched"
+    exit 1
+}
+
+ensure_latest_plugin "${MOBILE_CSS_PLUGIN}" "dsh-mobile-css"
+ensure_latest_plugin "${REMOTE_AUTH_PLUGIN}" "dsh-web-startup-auth"
+
+# nginx is the HF-facing listener. DSH remains behind it.
+nginx -g 'daemon off;' &
+NGINX_PID=$!
+trap 'kill "$NGINX_PID" 2>/dev/null || true' EXIT
+
+# dsh-web-startup-auth replaces the stock startup guard and provides:
+# - authenticated remote browser access
+# - remote settings/provider/credentials support
+# - crypto.randomUUID compatibility for non-loopback browser contexts
+# - loopback-authority handling for privileged APIs after authentication
+#
+# Bind DSH to all interfaces inside the container; nginx is the only public
+# HF-facing entry point. The auth plugin protects remote access.
+exec dsh --profile web --host 0.0.0.0 --port 3080 --no-open

nginx.conf

@@ -0,0 +1,41 @@
+worker_processes 1;
+pid /tmp/nginx.pid;
+
+events {
+    worker_connections 1024;
+}
+
+http {
+    include       /etc/nginx/mime.types;
+    default_type  application/octet-stream;
+
+    access_log /var/log/nginx/access.log;
+    error_log /var/log/nginx/error.log;
+
+    server {
+        listen 0.0.0.0:7860;
+
+        # DSH supports large file/workspace uploads.
+        client_max_body_size 160M;
+
+        location / {
+            proxy_pass http://127.0.0.1:3080;
+
+            proxy_http_version 1.1;
+            proxy_set_header Upgrade $http_upgrade;
+            proxy_set_header Connection "upgrade";
+
+            # Preserve the real HF authority. dsh-web-startup-auth performs
+            # the authenticated loopback-authority rewrite itself after login.
+            proxy_set_header Host $host;
+            proxy_set_header X-Real-IP $remote_addr;
+            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+            proxy_set_header X-Forwarded-Proto $scheme;
+
+            # Required for live token/event streaming and terminal/WebSocket traffic.
+            proxy_read_timeout 3600s;
+            proxy_send_timeout 3600s;
+            proxy_buffering off;
+        }
+    }
+}