Files
GitHop/docs/production-deployment.md
T
cyph3rasi 6be764ec6e Bind prompt history to Gitea's server-rendered session identity without an API token
Hop-State: A_06FNB7D05ZQ3AHD1V0GY5P8
Hop-Proposal: R_06FNB7CDK6ZKM505CPR2DY8
Hop-Task: T_06FNB715NCG0M3SVDJAGHY8
Hop-Attempt: AT_06FNB715NCK5MKAVH59TE0G
2026-07-12 02:17:01 -07:00

52 lines
1.7 KiB
Markdown

# Production deployment
Run the Compose stack behind an HTTPS reverse proxy. Keep the Gitea HTTP port
and Hop control-plane port bound to loopback; only publish Gitea's SSH port if
the deployment has a DNS-only hostname that can reach it without an HTTP
proxy.
Start from `.env.example`, replace every secret, and set at least:
```dotenv
GITEA_DOMAIN=git.example.com
GITEA_ROOT_URL=https://git.example.com/
GITEA_HTTP_BIND=127.0.0.1
HOP_HTTP_BIND=127.0.0.1
GITEA_SSH_BIND=127.0.0.1
GITEA_DISABLE_SSH=true
GITEA_DISABLE_REGISTRATION=true
GITEA_ACTIONS_ENABLED=false
```
Start the services and install the Hop-native Gitea assets:
```sh
docker compose --env-file .env up --build -d
./deploy/gitea/install-hop-native.sh
```
The reverse proxy should forward the public hostname to the configured
`GITEA_HTTP_BIND:GITEA_HTTP_PORT`, preserve the `Host` header, and set
`X-Forwarded-Proto` to `https`. It must also proxy `/hop/` to the Hop control
plane, preserving the browser's Gitea session cookie. This lets the Prompts
view check the viewer's repository access before returning potentially
sensitive prompt text.
The control plane verifies the browser session through Gitea's protected web
settings route. Hop's custom Gitea header renders the active account's immutable
user ID into that protected response, so browser-session verification does not
depend on Gitea's token-only `/api/v1/user` endpoint or `GITEA_API_TOKEN`.
For nginx, the control-plane location should precede the Gitea catch-all:
```nginx
location /hop/ {
proxy_pass http://127.0.0.1:8080/;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Cookie $http_cookie;
}
```
Persistent repository and database data live in the named Compose volumes.