Publish curated ITWorx-ModelForge source from 990401737f96c8d46a9f7b0d84994516cadcb6a0

docker-compose.production.yml

@@ -8,8 +8,8 @@
 # working tree. It still requires separate database secrets; this overlay additionally turns on
 # every production startup rule and requires immutable release identities.
 #
-# Every secret here uses the ${VAR:?message} form, so Compose refuses to render the project at all
-# when one is missing. Failing before the first container starts is the cheapest possible failure.
+# Database, backup and origin requirements fail Compose rendering when absent. Human authentication
+# accepts either a bootstrap key or a named administrator registry, validated before API startup.
 services:
   postgres:
     environment:
@@ -37,7 +37,8 @@ services:
   api:
     image: ${MODELFORGE_API_IMAGE:-modelforge-api:${MODELFORGE_VERSION:?set an exact release version, for example 1.2.1}}
     build:
-      context: ./backend
+      context: .
+      dockerfile: backend/Dockerfile
       args:
         MODELFORGE_VERSION: ${MODELFORGE_VERSION:-0.0.0}
         MODELFORGE_COMMIT: ${MODELFORGE_COMMIT:-}
@@ -47,7 +48,8 @@ services:
       # production deployment silently runs under development semantics.
       MODELFORGE_ENV: production
       MODELFORGE_DATABASE_URL: ${MODELFORGE_RUNTIME_DATABASE_URL:?set a URL for only the modelforge_runtime role}
-      MODELFORGE_OPERATOR_API_KEY: ${MODELFORGE_OPERATOR_API_KEY:?generate an operator API key; see docs/CONFIGURATION.md}
+      # Startup validates a legacy key OR an unexpired named administrator.
+      MODELFORGE_OPERATOR_API_KEY: ${MODELFORGE_OPERATOR_API_KEY:-}
       MODELFORGE_BACKUP_ENCRYPTION_KEY: ${MODELFORGE_BACKUP_ENCRYPTION_KEY:?generate a backup encryption key; without it no backup can be produced}
       MODELFORGE_CORS_ORIGINS: ${MODELFORGE_CORS_ORIGINS:?set the exact console origin; a wildcard is refused in production}
       # Remote model code is never executed in production. Stated here as well as enforced at