-
Notifications
You must be signed in to change notification settings - Fork 446
Closed
Description
This came up in #1470 — there's an inconsistency/ambiguity in how env files are handled across examples.
The current heuristic (as @badmonster0 explained) is: if an example contains XYZ_API_KEY, we provide a .env.example and expect users to copy it over to .env. Otherwise, we just use .env directly. This doesn't seem to be applied consistently; some examples document it:
| # Copy this to .env and fill in your actual database connection string |
...others don't.
I'm thinking we either standardize on .env.example everywhere (with clear comments like the above ^) or document a consistent pattern in a central place.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels