Tweak env vars section of docs (#611)

Thanks for the PR! 🍡
This commit is contained in:
Antonia Blair 2016-06-11 23:50:25 -04:00 committed by Daniel Roy Greenfeld
parent 29eb48efe8
commit b100f2a00d
2 changed files with 9 additions and 5 deletions

View File

@ -48,6 +48,7 @@ Listed in alphabetical order.
Andrew Mikhnevich `@zcho`_
Andy Rose
Anna Callahan `@jazztpt`_
Antonia Blair `@antoniablair`_ @antoniablairart
Areski Belaid `@areski`_
Ashley Camba
Barclay Gauld `@yunti`_
@ -128,6 +129,7 @@ Listed in alphabetical order.
.. _@alb3rto: https://github.com/alb3rto
.. _@amjith: https://github.com/amjith
.. _@andor-pierdelacabeza: https://github.com/andor-pierdelacabeza
.. _@antoniablair: https://github.com/antoniablair
.. _@areski: https://github.com/areski
.. _@arruda: https://github.com/arruda
.. _@bloodpet: https://github.com/bloodpet

View File

@ -35,11 +35,13 @@ But if you want to go further with setup, read on.
Setting Up Env Vars for Production
-----------------------------------
`Cookiecutter Django` uses the excellent `django-environ`_ package with its ``DATABASE_URL`` environment variable to simplify database configuration in your Django settings. Now all you have to do is rename env.example to .env and then compose a definition for ``DATABASE_URL`` as shown below and add it to the .env file:
`Cookiecutter Django` uses the excellent `django-environ`_ package, which includes a ``DATABASE_URL`` environment variable to simplify database configuration in your Django settings.
Rename env.example to .env to begin updating the file with your own environment variables. To add your database, define ``DATABASE_URL`` and add it to the .env file, as shown below:
.. parsed-literal::
$ export DATABASE_URL="postgres://*<pg_user_name>*:*<pg_user_password>*\ @127.0.0.1:\ *<pg_port>*/*<pg_database_name>*"
DATABASE_URL="postgres://*<pg_user_name>*:*<pg_user_password>*\ @127.0.0.1:\ *<pg_port>*/*<pg_database_name>*"
.. _django-environ: http://django-environ.readthedocs.io