ODS V3 Pre-Release: Public testing and refinement ahead of the official V3 launch. Turn your PC, Mac, or Linux box into a private AI server.
Python ai-agentsamdcomfyuidockerllama-cppllmlocal-ain8nnvidiaopen-webuiragself-hostedspeech-to-textstrix-halotext-to-speechworkflow-automation
# ODS — LAN-facing reverse proxy (host-based routing)
#
# Each ODS surface gets its own subdomain on the device's mDNS
# hostname. That way every backend stays root-mounted (no Open WebUI
# subpath gymnastics, no React Router base-href games) and the
# `ods-session` cookie can be Domain-scoped to <device>.local so SSO
# works across all of them.
#
# Hostnames the proxy answers (all pointing at the device's LAN IP via
# ods-mdns or equivalent DNS/hosts records):
#
# <device>.local — bare hostname: 302 redirect to chat
# chat.<device>.local — Open WebUI (root-mounted)
# dashboard.<device>.local— ODS Dashboard (operator UI)
# talk.<device>.local — ODS Talk mobile owner-card portal
# auth.<device>.local — dashboard-api: magic-link redemption
# + /api/auth/verify-session
# api.<device>.local — dashboard-api: /api/* admin surface
# hermes.<device>.local — hermes-proxy (only when enabled)
#
# Each block listens on the proxy's port (default :80) and matches on
# the Host header. We do NOT route by path on the bare hostname —
# trying to subpath-mount Open WebUI under /chat broke websockets,
# static asset paths, and OAuth callbacks (see audit on #1172).
#
# Security posture:
# * Proxy is the LAN-facing surface; everything behind it stays
# loopback-bound on the host.
# * Trust is delegated to each backend's existing checks: dashboard
# sign-in (dashboard/talk hosts use the dashboard's :3011 network
# listener) and dashboard-api's API key, Open WebUI's WEBUI_AUTH, and
# mandatory Hermes session gating on the LAN entrypoint.
# * For exposure beyond the trusted LAN, put this behind Tailscale.
# Don't publish to the public internet without TLS + extra auth.
{
# HTTP only by default. TLS via tailscale-cert / Caddy-issued certs
# is documented in docs/ODS-PROXY.md.
auto_https off
admin off
# Use the placeholder so a Caddyfile with no ODS_DEVICE_NAME still
# parses; substitution happens at server start.
log {
output stdout
format console
level INFO
}
}
# Variable: device-name segment used to build the per-service hostnames.
# Operators set ODS_DEVICE_NAME in .env; the compose passes it through.
# Falls back to "ods" so the proxy comes up even if .env is incomplete.
# ---------------------------------------------------------------------
# Health endpoint — anonymous, served on every hostname for probe ease.
# ---------------------------------------------------------------------
:80 {
@health path /health
handle @health {
respond "ok" 200
}
# Fall through to the host-matched blocks below.
}
# ---------------------------------------------------------------------
# chat.<device>.local → Open WebUI (root-mounted)
# ---------------------------------------------------------------------
http://chat.{$ODS_DEVICE_NAME:ods}.local {
# Cap request body at 200 MB — enough for document uploads to Open WebUI
# while preventing abuse of the LLM proxy paths from runaway clients.
request_body {
max_size 200MB
}
reverse_proxy open-webui:8080 {
header_up X-Forwarded-Proto {scheme}
header_up X-Forwarded-Host {host}
# Caddy auto-handles WebSocket upgrades; Open WebUI's streaming
# endpoints work without extra config.
}
}
# ---------------------------------------------------------------------
# dashboard.<device>.local → ODS Dashboard (operator UI)
# ---------------------------------------------------------------------
http://dashboard.{$ODS_DEVICE_NAME:ods}.local {
# :3011 is the dashboard's network listener: its admin API always
# requires dashboard sign-in (see the dashboard's nginx.conf).
reverse_proxy dashboard:3011 {
header_up X-Forwarded-Proto {scheme}
header_up X-Forwarded-Host {host}
}
}
# ---------------------------------------------------------------------
# talk.<device>.local → ODS Talk mobile owner-card portal
#
# Served by the dashboard container but rendered as a chrome-free route.
# /api/* requests still proxy to dashboard-api through dashboard nginx;
# the talk router ignores admin API-key auth and requires ods-session.
# The network listener (:3011) keeps the rest of the admin API behind
# dashboard sign-in on this hostname too.
# ---------------------------------------------------------------------
http://talk.{$ODS_DEVICE_NAME:ods}.local {
reverse_proxy dashboard:3011 {
header_up X-Forwarded-Proto {scheme}
header_up X-Forwarded-Host {host}
}
}
# ---------------------------------------------------------------------
# auth.<device>.local → dashboard-api (magic-link redemption surface)
#
# This is the host where the ods-session cookie is SET by redemption.
# session_signer sets Domain=<device>.local on the cookie so it also
# reaches chat.<device>.local, hermes.<device>.local, etc.
# ---------------------------------------------------------------------
http://auth.{$ODS_DEVICE_NAME:ods}.local {
reverse_proxy dashboard-api:3002 {
header_up X-Forwarded-Proto {scheme}
header_up X-Forwarded-Host {host}
}
}
# ---------------------------------------------------------------------
# api.<device>.local → dashboard-api (admin /api/* surface)
#
# Same upstream as auth.<device>.local; separated by hostname for
# operator-doc clarity ("invites/QR/etc. live at auth, admin status
# live at api"). Both call into the same FastAPI app; routing the
# whole hostname keeps the backend root-mounted.
# ---------------------------------------------------------------------
http://api.{$ODS_DEVICE_NAME:ods}.local {
# Cap request body at 50 MB for the admin API surface.
request_body {
max_size 50MB
}
reverse_proxy dashboard-api:3002 {
header_up X-Forwarded-Proto {scheme}
header_up X-Forwarded-Host {host}
}
}
# ---------------------------------------------------------------------
# hermes.<device>.local → hermes-proxy (only effective when the
# hermes-proxy extension is enabled; the upstream resolves via Docker
# DNS and 502s when the container isn't running, which is correct).
# ---------------------------------------------------------------------
http://hermes.{$ODS_DEVICE_NAME:ods}.local {
# The LAN entry must enforce a session even when the local-only Hermes
# listener is configured for convenient direct access.
forward_auth dashboard-api:3002 {
uri /api/auth/verify-session
# Hermes chat opens WebSockets. Send the auth sub-request as plain
# HTTP, or dashboard-api rejects the Upgrade handshake with 403 and a
# valid session is refused (same strips as hermes-proxy's own check).
header_up -Connection
header_up -Upgrade
header_up -Sec-Websocket-Key
header_up -Sec-Websocket-Version
header_up -Sec-Websocket-Protocol
header_up -Sec-Websocket-Extensions
}
reverse_proxy hermes-proxy:9120 {
header_up X-Forwarded-Proto {scheme}
header_up X-Forwarded-Host {host}
}
}
# ---------------------------------------------------------------------
# Bare <device>.local — the friendliest URL. Redirect to chat (the
# surface most users want). Operators who'd rather land on dashboard
# can edit this block or front the proxy with their own routing.
# ---------------------------------------------------------------------
http://{$ODS_DEVICE_NAME:ods}.local {
# The container always listens on :80. Preserve its published host port
# when sending the browser to the chat hostname.
redir http://chat.{$ODS_DEVICE_NAME:ods}.local:{$ODS_PROXY_PORT:80}{uri} 302
}