Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upStop using the odd `.env.tpl` file #120
Closed
Assignees
Labels
Comments
|
I believe we don't use |
|
Its explained as the default method to keep the variable in the README.md |
|
that must be fixed! |
|
(@bzz as you explained to me I moved this issue to backlog after adding to the project) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As explained here:
#36 (comment)
The usage of env file, populated with empty env vars is odd, and not very Devops friendly since handly configuration files is a something to be avoided, even if it contains env vars.
The env vars should be explicitly defined in all the examples, and be omitted if contains the default value or are empty, in the same that this should be explicitly defined in the `.travis.yml.