# Team Tryouts — environment variables # # Copy to .env and fill in. Every value here is a PRODUCTION-SAFE default: # copying this file and changing nothing gives a locked-down configuration # that refuses to start until the two required secrets are set, rather than # a working one that happens to be wide open (OPS-003). # # The previous version shipped FLASK_DEBUG=true under a heading that said # "fill in the values for production". The Werkzeug debugger executes code # submitted through the browser, so that one line turned a copy-paste into a # remote shell. # # For local development, see the DEVELOPMENT block at the bottom. # ============================================================================= # Required — the application refuses to start without these # ============================================================================= # Generate with: python -c "import secrets; print(secrets.token_hex(32))" # Never reuse one between environments: this key signs session cookies, so # whoever holds it can forge a session for any account. SECRET_KEY= # Expected form: postgresql://user:password@host:5432/database # The psycopg 3 driver is named for you by create_app(); postgresql:// alone # would send SQLAlchemy looking for psycopg2, which is not installed. DATABASE_URL= # ============================================================================= # Security — these defaults assume HTTPS in front. Do not relax them on a # deployed instance. # ============================================================================= # Session cookies are only sent over HTTPS. SESSION_COOKIE_SECURE=true # Plain HTTP is redirected to HTTPS. FORCE_HTTPS=true # The Werkzeug debugger is a remote code execution primitive by design. # Never true on anything reachable from a network you do not control. FLASK_DEBUG=false # Inline