OUTCOMES
What this Prompt helps you deliver
- Runtime configuration has one clear source
- Data, files, and domains can be verified end to end
BEFORE YOU START
Before you start
- The target deployment environment is known
- You can administer the database, storage, or domain
What AI should inspect first
.envdocker-compose.dev.ymldocker-compose.deploy.ymldeploymentapps/tabtin_djangoREADY TO RUN
Complete Prompt
Copy the complete Prompt with its execution and acceptance boundaries.
Configure the infrastructure for my TabTin product without giving each app a conflicting .env. Read AGENTS.md, .env, docker-compose.dev.yml, docker-compose.deploy.yml, deployment, and apps/tabtin_django. Separate development, test, staging, and production and classify each variable by owner, consumer, default, and sensitivity. Never print existing secrets or commit production credentials.
Use the root/deployment configuration as the single source. Configure PostgreSQL, Redis, uploads/object storage, persistence, capacity, and permissions. Configure Web, API, realtime, and public-share domains including HTTPS, CORS, trusted hosts, and callbacks. Inject secrets externally with rotation guidance and provide safe defaults only for non-secrets. Identify when Electron, Web, and mobile read variables and which changes require restart or rebuild.
Start the target environment and verify API health, database read/write, cache, upload/download, public URL, and realtime. Restart to prove persistence and test a missing variable or bad domain for a useful failure. Scan artifacts and logs for secrets. Report environment matrix, ownership, data locations, domain topology, secret handling, restart requirements, results, and exact production differences—without secret values.