From 6f46913b80ee52814e4711c110623751b9249b90 Mon Sep 17 00:00:00 2001
From: Pouzor <remy.jardinet@gmail.com>
Date: Mon, 9 Mar 2026 11:45:35 +0100
Subject: [PATCH] fix: use env_file in docker-compose to avoid bcrypt hash
 dollar-sign misparse

Docker Compose interpolates \$ in environment values as variable refs, breaking
the bcrypt hash (\$2b\$12\$...). Switching to env_file passes values verbatim.
---
 docker-compose.yml | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/docker-compose.yml b/docker-compose.yml
index 9ef080d..9cd9a06 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -4,14 +4,12 @@ services:
       context: .
       dockerfile: Dockerfile.backend
     restart: unless-stopped
+    env_file:
+      - .env
     environment:
-      SECRET_KEY: ${SECRET_KEY:?SECRET_KEY must be set in the environment or a .env file}
+      # Override env_file values that differ in Docker
       SQLITE_PATH: /app/data/homelab.db
       CORS_ORIGINS: '["http://localhost:3000"]'
-      AUTH_USERNAME: ${AUTH_USERNAME:-admin}
-      AUTH_PASSWORD_HASH: ${AUTH_PASSWORD_HASH}
-      SCANNER_RANGES: ${SCANNER_RANGES:-["192.168.1.0/24"]}
-      STATUS_CHECKER_INTERVAL: ${STATUS_CHECKER_INTERVAL:-60}
     volumes:
       - backend_data:/app/data
     networks: