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

Make sure all in-use env vars are represented in env.sample #77

Closed
MikeTheCanuck opened this issue May 6, 2018 · 2 comments
Closed

Comments

@MikeTheCanuck
Copy link
Contributor

There are at least two "new" environment variables in play this year, that might or might not be relevant to local development usage:
#51 (comment) (comment entitled "New env vars in play this year").

There may be others that weren't captured, that are documented in this comment:
#51 (comment)

@znmeb
Copy link
Contributor

znmeb commented May 22, 2018

Can we close this? I think we have all the environment variables documented.

@nam20485
Copy link
Member

Closing. All existing variables to-date are represented and comment added for description in the sample.env

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

No branches or pull requests

3 participants