## ## Einstellung die für das gesamte Projekt gelten. Also der Name und der Admin ## Das Environment muss "production","staging" oder "development" heißen INFRASTRUCTURE_LABEL=mindboost ENVIRONMENT=development ADMIN_USER=${INFRASTRUCTURE_LABEL:-default}_${ENVIRONMENT:-development} ADMIN_PASSWORD_HASH='$2y$05$U7noO29Ru/4VB5x8TpZo3.b4VjH6AAnhufJJUG2Vs7qHCM2Cd8yIK' # for development = admin SERVER_IP=127.0.0.1 ################################################################################################# # 🔧 ENVIRONMENT VARIABLES 🔧 # ################################################################################################# # # This file contains **default (fallback) values** for environment variables. # These values ensure that services run with sane defaults if no other configuration is provided. # # 📌 **ENVIRONMENT VARIABLE PRIORITY ORDER (Lowest to Highest)** # 1️⃣ **Fallback Values in the File** (Used only if no other source provides a value) # 2️⃣ **Global Defaults in `.env.all`** (Shared settings across all services) # 3️⃣ **Service-Specific `.env` Files** (Overrides per service group, e.g., `.env.backend`, `.env.proxy`) # 4️⃣ **Preloaded Shell Environment** (`export VAR=value` before running `docker compose`) # 5️⃣ **CLI Overrides** (`docker compose --env-file` or `-e VAR=value` → Highest Priority) # # 🔄 **Overwriting Behavior** # - Variables defined in **`.env.all`** override values in this file. # - Variables defined in **`.env.`** (e.g., `.env.backend`) override `.env.all`. # - Variables explicitly **exported in the shell** take priority over all `.env` files. # - Variables passed via **CLI (`--env-file` or `-e VAR=value`)** have the **highest priority**. # # 🚀 **Key Takeaways** # ✅ Use `.env.all` for common values across environments. # ✅ Use `.env.` for service-specific configurations. # ✅ If needed, manually override variables in the shell or CLI. # #################################################################################################