-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dotenv should look up in parent directories for .env #165
Comments
Yep, you're right. Will bring that feature in as a breaking change |
Hi, any updates? |
I've been umming and ahhing on this one. I know I was very supportive when originally opened, but ever since I've been worrying about directory traversal attacks. I'm about to close the door on breaking changes (see #182) but will hopefully include this one before I do (if I can come to comfort on the traversal risks) |
@joho what's your comfort level at around this now? I'm running into the same issue here with wanting my |
My
.env
file is at the root of my project, but when running tests, the current working directory is within test modules.This would match the behavior of https://github.com/dotenv-rs/dotenv/tree/3c1a77bc95821777e5ceb996c5e0b082f2a3ea38#usage and https://github.com/theskumar/python-dotenv.
The text was updated successfully, but these errors were encountered: