fix(deploy): write WEBCLAW_API_KEY in generated .env, not WEBCLAW_AUTH_KEY

setup.sh and deploy/hetzner.sh emitted WEBCLAW_AUTH_KEY into the server's
.env, but webclaw-server reads WEBCLAW_API_KEY (env = "WEBCLAW_API_KEY").
The generated key was silently ignored — and since hetzner.sh binds
0.0.0.0, the server refused to start at all (it rejects a public bind
without WEBCLAW_API_KEY). Fix both .env writers, plus the hetzner help
line that told users to grep the wrong name and the env.example sample.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Valerio 2026-06-20 14:43:55 +02:00
parent 3caca67cd1
commit a8eb6b3cfa
3 changed files with 4 additions and 4 deletions

View file

@ -29,7 +29,7 @@ OLLAMA_MODEL=qwen3:8b
# --- Server (webclaw-server only) ---
# WEBCLAW_PORT=3000
# WEBCLAW_HOST=0.0.0.0
# WEBCLAW_AUTH_KEY=your-auth-key
# WEBCLAW_API_KEY=your-auth-key
# WEBCLAW_MAX_CONCURRENCY=50
# WEBCLAW_JOB_TTL_SECS=3600
# WEBCLAW_MAX_JOBS=100