mirror of
https://github.com/cookiecutter/cookiecutter-django.git
synced 2024-11-26 11:34:00 +03:00
82dcd2d30c
When creating a Mailgun add-on on Heroku, the app gets some environment
variables by default:
MAILGUN_API_KEY
MAILGUN_DOMAIN
However, the cookiecutter names do not match and requires a manual step
from the user deploying. It's used elsewhere but shouldn't harm the
other deployment methods to rename these variables.
While updating the docs I noticed a variable that appear unused
DJANGO_MAILGUN_SERVER_NAME so this removes it from the documentation.
47 lines
1.1 KiB
Plaintext
47 lines
1.1 KiB
Plaintext
|
|
# PostgreSQL
|
|
POSTGRES_PASSWORD=!!!SET POSTGRES_PASSWORD!!!
|
|
POSTGRES_USER=!!!SET POSTGRES_USER!!!
|
|
CONN_MAX_AGE=
|
|
|
|
# Gunicorn concurrency
|
|
WEB_CONCURRENCY=4
|
|
|
|
# Domain name, used by caddy
|
|
DOMAIN_NAME={{ cookiecutter.domain_name }}
|
|
|
|
# General settings
|
|
# DJANGO_READ_DOT_ENV_FILE=True
|
|
DJANGO_ADMIN_URL=
|
|
DJANGO_SETTINGS_MODULE=config.settings.production
|
|
DJANGO_SECRET_KEY=!!!SET DJANGO_SECRET_KEY!!!
|
|
DJANGO_ALLOWED_HOSTS=.{{ cookiecutter.domain_name }}
|
|
|
|
# AWS Settings
|
|
DJANGO_AWS_ACCESS_KEY_ID=
|
|
DJANGO_AWS_SECRET_ACCESS_KEY=
|
|
DJANGO_AWS_STORAGE_BUCKET_NAME=
|
|
|
|
# Used with email
|
|
MAILGUN_API_KEY=
|
|
DJANGO_SERVER_EMAIL=
|
|
MAILGUN_DOMAIN=
|
|
|
|
# Security! Better to use DNS for this task, but you can use redirect
|
|
DJANGO_SECURE_SSL_REDIRECT=False
|
|
|
|
# django-allauth
|
|
DJANGO_ACCOUNT_ALLOW_REGISTRATION=True
|
|
{% if cookiecutter.use_sentry_for_error_reporting == 'y' -%}
|
|
# Sentry
|
|
DJANGO_SENTRY_DSN=
|
|
{% endif %}
|
|
{% if cookiecutter.use_opbeat == 'y' -%}
|
|
DJANGO_OPBEAT_ORGANIZATION_ID=
|
|
DJANGO_OPBEAT_APP_ID=
|
|
DJANGO_OPBEAT_SECRET_TOKEN=
|
|
{% endif %}
|
|
{% if cookiecutter.use_compressor == 'y' -%}
|
|
COMPRESS_ENABLED=
|
|
{% endif %}
|