django-environ 0.6.0

A package that allows you to utilize 12factor inspired environment variables to configure your Django application.

django-environ is the Python package that allows you to use Twelve-factor methodology to configure your Django application with environment variables.

For that, it gives you an easy way to configure Django application using environment variables obtained from an environment file and provided by the OS:

import environ
import os

env = environ.Env(
    # set casting, default value
    DEBUG=(bool, False)
)

# Set the project base directory
BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))

# Take environment variables from .env file
environ.Env.read_env(os.path.join(BASE_DIR, '.env'))

# False if not in os.environ because of casting above
DEBUG = env('DEBUG')

# Raises Django's ImproperlyConfigured
# exception if SECRET_KEY not in os.environ
SECRET_KEY = env('SECRET_KEY')

# Parse database connection url strings
# like psql://user:pass@127.0.0.1:8458/db
DATABASES = {
    # read os.environ['DATABASE_URL'] and raises
    # ImproperlyConfigured exception if not found
    #
    # The db() method is an alias for db_url().
    'default': env.db(),

    # read os.environ['SQLITE_URL']
    'extra': env.db_url(
        'SQLITE_URL',
        default='sqlite:////tmp/my-tmp-sqlite.db'
    )
}

CACHES = {
    # Read os.environ['CACHE_URL'] and raises
    # ImproperlyConfigured exception if not found.
    #
    # The cache() method is an alias for cache_url().
    'default': env.cache(),

    # read os.environ['REDIS_URL']
    'redis': env.cache_url('REDIS_URL')
}

The idea of this package is to unify a lot of packages that make the same stuff: Take a string from os.environ, parse and cast it to some of useful python typed variables. To do that and to use the 12factor approach, some connection strings are expressed as url, so this package can parse it and return a urllib.parse.ParseResult. These strings from os.environ are loaded from a .env file and filled in os.environ with setdefault method, to avoid to overwrite the real environ. A similar approach is used in Two Scoops of Django book and explained in 12factor-django article.

Using django-environ you can stop to make a lot of unversioned settings_*.py to configure your app. See cookiecutter-django for a concrete example on using with a django project.

Feature Support

• Fast and easy multi environment for deploy

• Fill os.environ with .env file variables

• Variables casting

• Url variables exploded to django specific package settings

Project Information

django-environ is released under the MIT / X11 License, its documentation lives at Read the Docs, the code on GitHub, and the latest release on PyPI.

It’s rigorously tested on Python 3.5+, and officially supports Django 1.11, 2.2, 3.0, 3.1 and 3.2.

If you’d like to contribute to django-environ you’re most welcome!

Support

Should you have any question, any remark, or if you find a bug, or if there is something you can’t do with the django-environ, please open an issue.

Contributing

If you would like to contribute to django-environ, please take a look at the current issues. If there is a bug or feature that you want but it isn’t listed, make an issue and work on it.

How to Contribute

1. Check for open issues or open a fresh issue to start a discussion around a feature idea or a bug.

2. Fork the repository on GitHub to start making your changes to the develop branch (or branch off of it).

3. Write a test which shows that the bug was fixed or that the feature works as expected.

4. Send a pull request and bug the maintainer until it gets merged and published.

Release Information

v0.6.0 - 4-September-2021

Added

• Python 3.9, 3.10 and pypy 3.7 are now supported

• Django 3.1 and 3.2 are now supported

• Added missed classifiers to setup.py

• Accept Python 3.6 path-like objects for read_env

Fixed

• Fixed various code linting errors

• Fixed typos in the documentation

• Added missed files to the package contents

• Fixed db_url_config to work the same for all postgres-like schemes

Changed

• Refactor tests to use pytest and follow DRY

• Moved CI to GitHub Actions

• Restructuring of project documentation

• Build and test package documentation as a part of CI pipeline

• Build and test package distribution as a part of CI pipeline

• Check MANIFEST.in in a source package for completeness as a part of CI pipeline

• Added pytest and coverage[toml] to setuptools’ extras_require

Full changelog.

Security Policy

Reporting a Vulnerability

If you discover a security vulnerability within django-environ, please send an e-mail to Serghei Iakovlev via [e-mail]. All security vulnerabilities will be promptly addressed.

Credits

django-environ was initially created by Daniele Faraglia and currently maintained by Serghei Iakovlev.

A full list of contributors can be found in GitHub.

The existence of django-environ would have been impossible without these projects:

• rconradharris/envparse

• jacobian/dj-database-url

• migonzalvar/dj-email-url

• ghickman/django-cache-url

• dstufft/dj-search-url

• julianwachholz/dj-config-url

• nickstenning/honcho

• rconradharris/envparse