-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
Truly global .env configuration. #171
Comments
Yes! If I right-click on a unittest module, class, or function and run/debug it, it automatically creates a new run configuration. if it doesn't exist yet. So, I can easily have 20 different run configurations. This requested feature is really a deal-breaker for me. At this point, it seems the simplest way is to edit the |
Hello, |
Agreed, load default dot env file at root directory is very useful feature |
I guess that is related to #31 |
So who is working on this or what is involved in moving the ball forward? I can help write tests, documentation or code but this would be helpful in the management many projects. |
It seems to me that in virtually every situation you want to load the
.env
file if it is available in the working directory or project root. I'd love to have support for this in a way that just enables this cross-project and cross-pycharm-feature.Especially for those who manage many projects the best workflow you can currently have (as far as I know) is the following
After this you still have to manually load the .env config for some pycharm elements like the terminal.
I think that this concept of a cross-project default configuration can easily prevent 100 clicks for every new project in just the setup.
Additionally letting people pick the
.env
file using a path in plaintext rather than a file picker would also drastically lower the time it takes to do the setup.The text was updated successfully, but these errors were encountered: