chore: rename .env to .env.example #136
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.
Overview
This change moves the existing
.env
file to.env.example
while adding.env
to .gitignore. It also adds in an extra variablePGUSER=casekit
to the now.env.example
file. Adding this file allows updates to the .env file without committing it as well as making it more explicit what values are used for the connection since thenode-pg
package uses these environment variables by default for connection.