DGNum/gestioCOF
16
2
Fork 2
Code Issues 78 Pull requests 15 Projects Releases 12 Packages Wiki Activity
gestioCOF/cof/settings/prod.py

29 lines
730 B
Python
Raw Permalink Normal View History

New organisation of settings files We reproduce what has been done here: https://github.com/dissemin/dissemin The following files can be found under `cof/settings/` - `common.py`: the settings that are shared by all the environments we have + the secrets (see below). - `dev.py`: the settings used by the vagrant VM for local development. - `prod.py`: the production settings (for both www.cof.ens.fr and dev.cof.ens.fr) There is also a notion of "secrets". Some settings like the `SECRET_KEY` or the database's credentials are loaded from an untracked files called `secret.py` in the same directory. This secrets are loaded by the common settings file.
2017-04-10 23:18:00 +02:00
"""
Django development settings for the cof project.
The settings that are not listed here are imported from .common
"""
import os
Move STATIC_ROOT in production
2017-08-08 01:24:00 +02:00
from .common import * # NOQA
enable the "events" app in CI
2019-10-05 17:50:28 +02:00
from .common import BASE_DIR, INSTALLED_APPS, TESTING, import_secret
New organisation of settings files We reproduce what has been done here: https://github.com/dissemin/dissemin The following files can be found under `cof/settings/` - `common.py`: the settings that are shared by all the environments we have + the secrets (see below). - `dev.py`: the settings used by the vagrant VM for local development. - `prod.py`: the production settings (for both www.cof.ens.fr and dev.cof.ens.fr) There is also a notion of "secrets". Some settings like the `SECRET_KEY` or the database's credentials are loaded from an untracked files called `secret.py` in the same directory. This secrets are loaded by the common settings file.
2017-04-10 23:18:00 +02:00
DEBUG = False
core -- Apply black + isort to all files
2018-10-06 12:35:49 +02:00
ALLOWED_HOSTS = ["cof.ens.fr", "www.cof.ens.fr", "dev.cof.ens.fr"]
New organisation of settings files We reproduce what has been done here: https://github.com/dissemin/dissemin The following files can be found under `cof/settings/` - `common.py`: the settings that are shared by all the environments we have + the secrets (see below). - `dev.py`: the settings used by the vagrant VM for local development. - `prod.py`: the production settings (for both www.cof.ens.fr and dev.cof.ens.fr) There is also a notion of "secrets". Some settings like the `SECRET_KEY` or the database's credentials are loaded from an untracked files called `secret.py` in the same directory. This secrets are loaded by the common settings file.
2017-04-10 23:18:00 +02:00
enable the "events" app in CI
2019-10-05 17:50:28 +02:00
if TESTING:
New app: clubs - Clubs will be used both by the cof and the bds app. - For now, they are only visible in development.
2019-10-06 19:59:07 +02:00
INSTALLED_APPS += ["events", "clubs"]
Move STATIC_ROOT in production
2017-08-08 01:24:00 +02:00
STATIC_ROOT = os.path.join(
core -- Apply black + isort to all files
2018-10-06 12:35:49 +02:00
os.path.dirname(os.path.dirname(BASE_DIR)), "public", "gestion", "static"
Move STATIC_ROOT in production
2017-08-08 01:24:00 +02:00
)
New organisation of settings files We reproduce what has been done here: https://github.com/dissemin/dissemin The following files can be found under `cof/settings/` - `common.py`: the settings that are shared by all the environments we have + the secrets (see below). - `dev.py`: the settings used by the vagrant VM for local development. - `prod.py`: the production settings (for both www.cof.ens.fr and dev.cof.ens.fr) There is also a notion of "secrets". Some settings like the `SECRET_KEY` or the database's credentials are loaded from an untracked files called `secret.py` in the same directory. This secrets are loaded by the common settings file.
2017-04-10 23:18:00 +02:00
STATIC_URL = "/gestion/static/"
MEDIA_ROOT = os.path.join(os.path.dirname(BASE_DIR), "media")
MEDIA_URL = "/gestion/media/"
Upgrade to reCAPTCHA v2 reCAPTCHA v1 has been shut down since March 2018. We now uses reCAPTCHA v2: - user must check a simple checkbox (No CAPTCHA), - eventually he must validate a challenge. Moving keys settings allows to use the captcha for development. Fixes #192.
2018-05-14 13:22:59 +02:00
RECAPTCHA_PUBLIC_KEY = import_secret("RECAPTCHA_PUBLIC_KEY")
RECAPTCHA_PRIVATE_KEY = import_secret("RECAPTCHA_PRIVATE_KEY")
Reference in a new issue Copy permalink