feat: add .env-example #587
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: eb754ee The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://create-t3-app-git-fork-c-ehrlich-env-example-t3-oss.vercel.app/ |
nexxeln
requested changes
Oct 7, 2022
nexxeln
approved these changes
Oct 7, 2022
|
Should be added to the docs too perhaps? |
devvianto605
pushed a commit
to devvianto605/create-devviantex-nextjs-app-deprecated
that referenced
this pull request
Jun 9, 2024
* add .env-example * chore: changeset * expand .env-example explanation Co-authored-by: Shoubhit Dash <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #585
✅ Checklist
IIRC we only generated
.env-examplea while ago, and changed it to.envso that the app could be immediately started after scaffolding. Will close this PR if anyone has a good reason why we shouldn't include both.envand.env-exampleby default.Changelog
.env-examplefile with the same content as the normal.envfile plus a warning about not putting secrets in there.if (!envFile) return;guard clause up a few lines to prevent pointlessly generating the envContent before not saving it to anywhere.Screenshots
💯