docs: clarify .env.dev vs .env.example usage #6102
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added a brief note in
DEVELOPMENT.mdto clarify the distinction between.env.dev(for local development) and.env.example(for self-hosted Docker deployments).This helps new contributors avoid confusion when setting up the development environment, as the two files use different hostnames (
localhostvs Docker-internalpostgres).Changes
.env.devprerequisite inDEVELOPMENT.mdType of Change