Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings
Discussion options

hrkristoffer
Jan 26, 2024

In the module for managing the VSCode environment, a .env file is referenced. This file is not in the repo?
You must be logged in to vote

Replies: 2 comments · 3 replies

Comment options

mikeckennedy
Jan 26, 2024
Maintainer

Hi @hrkristoffer I believe .env files are generally not intended to be committed as they are a "safe" place to store both machine specific settings and passwords/tokens. @cecilphillip @clarkio can you guys confirm? :)
You must be logged in to vote
1 reply
@hrkristoffer
Comment options

hrkristoffer Jan 26, 2024
Author

Shure, but as the file is used in demonstration and, me assuming, that it only contains the demoed values, I thought it would be of no harm.
Comment options

mikeckennedy
Jan 26, 2024
Maintainer

That's fair. But the .gitignores from standard github projects all exclude them by default. It probably does make sense to check them in. @cecilphillip @clarkio do either of you have that file still?
You must be logged in to vote
2 replies
@cecilphillip
Comment options

cecilphillip Jan 26, 2024
Maintainer

I still have all the code. I'll add it when I get back later today.
@mikeckennedy
Comment options

mikeckennedy Jan 26, 2024
Maintainer

Thanks @cecilphillip !
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
🙏
Q&A
Labels
None yet
3 participants
@hrkristoffer @cecilphillip @mikeckennedy
Morty Proxy This is a proxified and sanitized view of the page, visit original site.