Skip to content
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

Add feature: specifying env file #1070

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Rockheung
Copy link

@Rockheung Rockheung commented Oct 2, 2022

Hello! This plugin is fantastic.

This pull request (PR) introduces enhancements to the way the dotenv file is imported, giving users the flexibility to choose any dotenv file that starts with .env. If no filename is specified, the default dotenv filename remains as .env.

Additionally, I have made updates to the readme file.

Please let me know if you have any further suggestions or if there's anything else I can assist you with!

@Xenion1987
Copy link

I'd like this feature as well.

@coma-toast
Copy link

This feature would greatly simplify configuration for my use case. I am trying to use this instead of (or at least to augment) Postman so that all API calls are documented in our repo, and tracked via git. Using custom variables repeatedly using one parent .env instead of copying and pasting in each folder/file would be a huge improvement.

@Rockheung Rockheung marked this pull request as draft July 6, 2023 06:35
@Rockheung Rockheung marked this pull request as ready for review July 6, 2023 06:35
@Diabl0570
Copy link

Do I understand correctly that this only supports a the direct parent dir? Or can this also go up multiple directories?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants