An .env file stores configuration as key-value pairs, including service endpoints, credentials, and runtime settings. Its variable names reveal candidate external integrations without exposing secret values. section 9.2
Use an .env file as an architectural lead, not conclusive proof:
- Scan variable names such as STRIPE_SECRET_KEY, SENDGRID_API_KEY, and OPENAI_API_KEY to identify candidate third-party services. section 9.2
- Check application imports and client construction to confirm that a configured integration is still used; stale variables can remain after deletion. section 9.2
- Combine the .env view with Compose, application code, and infrastructure definitions because no single file exposes the whole system. section 9.2
Reading dependency clues
DATABASE_URL and REDIS_URL identify database and cache connections, while STRIPE_SECRET_KEY, SENDGRID_API_KEY, and OPENAI_API_KEY suggest external integrations. The names establish candidates; code must verify them. section 9.2
Listing 9.2 A .env file listing external dependencies in its variable names.
DATABASE_URL=postgresql://postgres:5432/myapp REDIS_URL=redis://redis:6379 STRIPE_SECRET_KEY=sk_test_xxxxxxxxxxxx #A SENDGRID_API_KEY=SG.xxxxxxxxxxxx #B OPENAI_API_KEY=sk-proj-xxxxxxxxxxxx #C
Inspect a compact .env listing that demonstrates database, cache, and external-service variables. section 9.2





