-
Notifications
You must be signed in to change notification settings - Fork 505
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
template is not created in working directory #461
Comments
The documentation shows one creating a template from https://github.com/bkeepers/dotenv#should-i-commit-my-env-file So, were you to run the example code, then "A template will be created in your working directory named If you look at the code: Lines 9 to 17 in 45b712a
...then you will see that it just takes the filename passed on the CLI (including the path; the input file name After looking at it, I think that the current functionality is the expected behavior. |
Indeed, that is what the code does and what I pointed out to be be incompatible with the documentation. The template is not created in the working directory but in the directory where the .env lives. In the documentation example they happen to be the same. If this is the expected behavior the documentation could be updated, if the documentation is right, the code could be updated, but right now they are not compatible with each other. |
When I create a template from an existing
.env
file located in another directory as my working directory, the template is not created in my working directorySteps to reproduce
Expected behavior
I expected the
.env.template
to be created in my current (working) directory and not in the directory of the.env
file as per the documentation.System configuration
dotenv version:
dotenv 2.8.1
The text was updated successfully, but these errors were encountered: