Delete README.md

README.md

@@ -1,94 +0,0 @@
----
-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.