Document deployment proxy token

This commit is contained in:
hwhung
2026-05-06 20:55:34 +08:00
parent da856261f3
commit 657f81d4e0
2 changed files with 15 additions and 4 deletions
+4 -1
View File
@@ -65,12 +65,15 @@ These can be overridden with CLI flags or environment variables:
- `--port` or `PORT` - `--port` or `PORT`
- `--proxy-api-key` or `PROXY_API_KEY` - `--proxy-api-key` or `PROXY_API_KEY`
For mass deployments, set `PROXY_API_KEY` to the token generated by the deployment system. The
app will use that token as the required `Authorization: Bearer ...` value.
## Verify ## Verify
```bash ```bash
curl -s http://localhost:3000/api/healthz curl -s http://localhost:3000/api/healthz
curl -s http://localhost:3000/dashboard | head curl -s http://localhost:3000/dashboard | head
curl -s -H "Authorization: Bearer dev-proxy-key" http://localhost:3000/v1/models curl -s -H "Authorization: Bearer ${PROXY_API_KEY:-dev-proxy-key}" http://localhost:3000/v1/models
``` ```
Expected without provider flags: dashboard, health, and model list work; chat completions return `503`. Expected without provider flags: dashboard, health, and model list work; chat completions return `503`.
+11 -3
View File
@@ -2,6 +2,11 @@ Clone and run https://git.komnenos.me/springfw/random-proxy in ./random-proxy.
Goal: get the app running once, with Replit AI Integrations wired, on port 3000. Goal: get the app running once, with Replit AI Integrations wired, on port 3000.
The deployment system may provide a generated bearer token for this instance. Use that exact
token as the `PROXY_API_KEY` environment variable/secret. Do not invent, rotate, print, or
replace it. If no generated token is provided, leave `PROXY_API_KEY` unset and use the app
default only for verification.
Do not: Do not:
- add it to a parent workspace - add it to a parent workspace
- move it into artifacts/ - move it into artifacts/
@@ -20,13 +25,16 @@ Steps:
- OpenAI - OpenAI
- Anthropic - Anthropic
3. Open ./random-proxy and use the configured Replit Run button. 3. Set `PROXY_API_KEY` to the deployment-provided/generated token if one was provided.
4. Wait briefly, then verify: 4. Open ./random-proxy and use the configured Replit Run button.
5. Wait briefly, then verify. Use the generated token in the Authorization header when
`PROXY_API_KEY` was set; otherwise use `dev-proxy-key`:
curl -s http://localhost:3000/api/healthz curl -s http://localhost:3000/api/healthz
curl -s http://localhost:3000/dashboard | head curl -s http://localhost:3000/dashboard | head
curl -s -H "Authorization: Bearer dev-proxy-key" http://localhost:3000/v1/models curl -s -H "Authorization: Bearer ${PROXY_API_KEY:-dev-proxy-key}" http://localhost:3000/v1/models
Report only: Report only:
- local URL - local URL