Automated deployment update from ML build

Dockerfile

@@ -0,0 +1,27 @@
+FROM ghcr.io/open-webui/open-webui:main
+
+# 1. Hugging Face Spaces require the container to listen on Port 7860
+ENV PORT=7860
+EXPOSE 7860
+
+# 2. Point Open WebUI directly to your LiteLLM gateway
+ENV OPENAI_API_BASE_URL=https://samuellance73-mldemo.hf.space/v1
+ENV OPENAI_API_KEY=none
+
+# 3. Disable local authentication (using open/unprotected gateway)
+ENV WEBUI_AUTH=False
+
+# 4. Inject static security keys so the container never has to write them to disk on boot
+ENV WEBUI_SECRET_KEY=sanctuary_covert_vault_secret_key_99
+ENV OAUTH_SESSION_TOKEN_ENCRYPTION_KEY=sanctuary_oauth_token_encryption_key_99_secure_bytes
+
+# 5. FIX ALL PERMISSIONS: Switch to root to configure the entire app directory for UID 1000
+USER root
+
+# Grant full ownership and write permissions of the entire application directory to the HF user (1000)
+RUN mkdir -p /app/backend/data && \
+    chown -R 1000:1000 /app && \
+    chmod -R 777 /app
+
+# 6. Switch back to the unprivileged Hugging Face user (UID 1000) for execution
+USER 1000

README.md

@@ -1,10 +1,46 @@
 ---
-title: Open Webui
-emoji: 🏢
-colorFrom: gray
-colorTo: green
+title: Open WebUI
+emoji: 🤖
+colorFrom: indigo
+colorTo: purple
 sdk: docker
+app_port: 7860
 pinned: false
 ---
 
-Check out the configuration reference at https://huggingface.co/docs/hub/spaces-config-reference
+# Sanctuary Web UI
+
+This directory contains the standalone web interface configuration for the Sanctuary monorepo. 
+
+It is designed to deploy **Open WebUI** directly to a Hugging Face Space as a Docker container, acting as a clean, elegant frontend.
+
+## Architecture
+
+```
+Sanctuary/
+├── main/                   <─── Backend ML & deployment configuration
+└── web-ui/                 <─── Standalone frontend configuration (this folder)
+    ├── Dockerfile          <─── Port-configured Open WebUI Docker image
+    └── README.md           <─── Hugging Face Space metadata and documentation
+```
+
+By decoupling the web UI configuration from the backend Python scripts and custom obfuscation logic, we achieve:
+1. **Separation of Concerns**: The Python code remains 100% focused on core backend tasks, free from UI configs.
+2. **Independent Scalability**: Changes to the web UI config do not trigger backend rebuilds.
+3. **Clean Monorepo Layout**: Keeps physical files distinct while maintaining unified history and node configurations.
+
+## Local Configuration
+
+The parent deployment pipeline manages this directory using the `custom-dir` parameter in `main/manifests/nodes.yaml`:
+
+```yaml
+  web-ui:
+    hf-repo: "samuellance73/open-webui"
+    token-env: "HF1"
+    create-repo: true
+    space-sdk: docker
+    repo-type: space
+    custom-dir: "../web-ui"
+```
+
+When `deploy.py` is invoked, it resolves the relative path `../web-ui` from `main/` and uploads this configuration directly to the target space repository.