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 explantion of using .env to docs #18

Closed
pjbull opened this issue Apr 29, 2016 · 3 comments
Closed

Add explantion of using .env to docs #18

pjbull opened this issue Apr 29, 2016 · 3 comments

Comments

@pjbull
Copy link
Member

pjbull commented Apr 29, 2016

  • E.g., deployment secrets, access keys, SQL connection strings
isms added a commit that referenced this issue Apr 29, 2016
- Add opinion about being careful before changing folder layout.
@isms
Copy link
Contributor

isms commented Apr 29, 2016

@pjbull just added explanation here via 873cfd6 - thoughts?

@pjbull
Copy link
Member Author

pjbull commented Apr 29, 2016

👏 👏 👏

The one thought is that notebooks don't have __file__ defined so we should try to make a code snippet that plays nicely with both.

screen shot 2016-04-29 at 3 13 04 pm

isms added a commit that referenced this issue Apr 29, 2016
- Add `find_dotenv` method that will try to find a .env file by
  (a) guessing where to start using `__file__` or the working
  directory -- allowing this to work in non-file contexts such as
  IPython notebooks and the REPL, and then
  (b) walking up the directory tree looking for the specified file
  -- called `.env` by default. This is a bit like the "filthy magic"
  employed by django-dotenv[1] to serve the same purpose, and allows
  the user to write `load_dotenv(find_dotenv())` in many contexts.

[1] https://github.com/jpadilla/django-dotenv/blob/master/dotenv.py#L44-L46
isms added a commit that referenced this issue Apr 29, 2016
- Add `find_dotenv` method that will try to find a .env file by
  (a) guessing where to start using `__file__` or the working
  directory -- allowing this to work in non-file contexts such as
  IPython notebooks and the REPL, and then
  (b) walking up the directory tree looking for the specified file
  -- called `.env` by default. This is a bit like the "filthy magic"
  employed by django-dotenv[1] to serve the same purpose, and allows
  the user to write `load_dotenv(find_dotenv())` in many contexts.

[1] https://github.com/jpadilla/django-dotenv/blob/master/dotenv.py#L44-L46
isms added a commit that referenced this issue Apr 29, 2016
- Add `find_dotenv` method that will try to find a .env file by
  (a) guessing where to start using `__file__` or the working
  directory -- allowing this to work in non-file contexts such as
  IPython notebooks and the REPL, and then
  (b) walking up the directory tree looking for the specified file
  -- called `.env` by default. This is a bit like the "filthy magic"
  employed by django-dotenv[1] to serve the same purpose, and allows
  the user to write `load_dotenv(find_dotenv())` in many contexts.

[1] https://github.com/jpadilla/django-dotenv/blob/master/dotenv.py#L44-L46
isms added a commit that referenced this issue Apr 29, 2016
- Add `find_dotenv` method that will try to find a .env file by
  (a) guessing where to start using `__file__` or the working
  directory -- allowing this to work in non-file contexts such as
  IPython notebooks and the REPL, and then
  (b) walking up the directory tree looking for the specified file
  -- called `.env` by default. This is a bit like the "filthy magic"
  employed by django-dotenv[1] to serve the same purpose, and allows
  the user to write `load_dotenv(find_dotenv())` in many contexts.

[1] https://github.com/jpadilla/django-dotenv/blob/master/dotenv.py#L44-L46
@isms
Copy link
Contributor

isms commented Apr 29, 2016

Pull request added: #22

@isms isms closed this as completed in 880c55e May 1, 2016
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

2 participants