-
-
Notifications
You must be signed in to change notification settings - Fork 314
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d5de3dd
commit e28d633
Showing
9 changed files
with
259 additions
and
191 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10,6 +10,7 @@ The ``__init__`` module | |
|
||
.. automodule:: environ | ||
:members: | ||
:special-members: | ||
:no-undoc-members: | ||
|
||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
=== | ||
FAQ | ||
=== | ||
|
||
|
||
#. **Can django-environ determine the location of .env file automatically?** | ||
|
||
``django-environ`` will try to get and read ``.env`` file from the project | ||
root if you haven't specified the path for it when call :meth:`.environ.Env.read_env`. | ||
However, this is not the recommended way. When it is possible always specify | ||
the path tho ``.env`` file. Alternatively, you can use a trick with a | ||
environment variable pointing to the actual location of ``.env`` file. | ||
For details see ":ref:`multiple-env-files-label`". | ||
|
||
#. **What (where) is the root part of the project, is it part of the project where are settings?** | ||
|
||
Where your ``manage.py`` file is (that is your project root directory). | ||
|
||
#. **What kind of file should .env be?** | ||
|
||
``.env`` is a plain text file. | ||
|
||
#. **Should name of the file be simply .env (or something.env)?** | ||
|
||
Just ``.env``. However, this is not a strict rule, but just a common | ||
practice. Formally, you can use any filename. | ||
|
||
#. **Is .env file going to be imported in settings file?** | ||
|
||
No need to import, ``django-environ`` automatically picks variables | ||
from there. |
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.