antialias
/
soroban-abacus-flashcards
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(litefs): remove HOSTNAME env var to allow pod hostname detection 

LiteFS needs the actual pod hostname for cluster communication,
but HOSTNAME=0.0.0.0 was being set in both the Dockerfile and
ConfigMap, overriding the pod's hostname.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Thomas Hallock 2026-01-21 14:38:30 -06:00
parent 8b39673c8d
commit 42f55855eb
2 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Dockerfile
View File

@ -199,7 +199,7 @@ EXPOSE 3000
# LiteFS proxy listens on 8080, app on 3000 # LiteFS proxy listens on 8080, app on 3000
EXPOSE 8080 EXPOSE 8080
ENV PORT=3000 ENV PORT=3000
ENV HOSTNAME="0.0.0.0" # Note: Don't set HOSTNAME here - LiteFS needs the pod's actual hostname
ENV NODE_ENV=production ENV NODE_ENV=production
# Default: run without LiteFS (for local dev and Docker Compose) # Default: run without LiteFS (for local dev and Docker Compose)

3
infra/terraform/app.tf
View File

@ -27,7 +27,8 @@ resource "kubernetes_config_map" "app_config" {
data = { data = {
NODE_ENV = "production" NODE_ENV = "production"
PORT = "3000" PORT = "3000"
HOSTNAME = "0.0.0.0" # Note: Don't set HOSTNAME here - it conflicts with LiteFS which needs the pod hostname
# Next.js will use 0.0.0.0 by default if HOSTNAME is not set
NEXT_TELEMETRY_DISABLED = "1" NEXT_TELEMETRY_DISABLED = "1"
REDIS_URL = "redis://redis:6379" REDIS_URL = "redis://redis:6379"
# LiteFS mounts the database at /litefs # LiteFS mounts the database at /litefs