From 3df1b9fb92ccc5308c2550b90f61d365ff3f4fbb Mon Sep 17 00:00:00 2001 From: michael Date: Tue, 16 Dec 2025 06:37:41 -0600 Subject: [PATCH] Auto-generate .env for docker compose commands MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The deploy script now creates a .env file with COMPOSE_PROJECT_NAME and BACKEND_PORT so that manual docker compose commands (ps, logs, etc.) work without needing to set environment variables. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 --- deploy.sh | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/deploy.sh b/deploy.sh index e3632c7..e0373ad 100755 --- a/deploy.sh +++ b/deploy.sh @@ -43,11 +43,20 @@ if [ -z "$FRONTEND_DEPLOY_DIR" ]; then exit 1 fi -# Export variables for docker compose -export COMPOSE_PROJECT_NAME="${COMPOSE_PROJECT_NAME:-modcomms}" -export BACKEND_PORT="${BACKEND_PORT:-8000}" +# Set defaults for docker compose variables +COMPOSE_PROJECT_NAME="${COMPOSE_PROJECT_NAME:-modcomms}" +BACKEND_PORT="${BACKEND_PORT:-8000}" echo " Environment: ${COMPOSE_PROJECT_NAME} (port ${BACKEND_PORT})" +# Create .env file for docker compose (so manual docker compose commands work) +cat > .env << EOF +# Auto-generated by deploy.sh - do not edit manually +# Edit .env.deploy instead and re-run deploy.sh +COMPOSE_PROJECT_NAME=${COMPOSE_PROJECT_NAME} +BACKEND_PORT=${BACKEND_PORT} +EOF +echo " ✓ .env created for docker compose" + # --- Check backend/.env exists (required for GEMINI_API_KEY) --- if [ ! -f backend/.env ]; then if [ -f backend/.env.example ]; then