Add optional API key auth to the server
build / build (push) Successful in 3m4s

Deployments reachable outside a trusted LAN need some form of access
control. Set FUELISH_API_KEY and the server requires a matching
X-API-Key header on /jobs; unset, behavior is unchanged (no auth).
The Android app gets a matching Settings field. This only checks the
key - TLS termination is left to a reverse proxy in front of the
server, not handled here.
This commit is contained in:
ml
2026-10-04 11:41:55 +02:00
parent ca85530b5a
commit 7a91a37049
13 changed files with 111 additions and 25 deletions
+7
View File
@@ -0,0 +1,7 @@
# Copy to .env (gitignored, never commit the real value) to require an
# API key on the server's /jobs endpoint - see docker-compose.yml and
# tooling-container/src/server.py. Leave FUELISH_API_KEY unset/empty for
# the original LAN-only/no-auth setup.
#
# Generate one with: openssl rand -hex 32
FUELISH_API_KEY=