Skip to content
Snippets Groups Projects
Commit 3c2b4569 authored by Daniel Wysocki's avatar Daniel Wysocki
Browse files

Adding 'TIER' setting constant to each type of deployment

This is for easy programmatic access to the tier name.
parent aee17a51
No related branches found
No related tags found
1 merge request!99Adding 'TIER' setting constant to each type of deployment
# Settings for a test/dev GraceDB instance running in a container
from .base import *
TIER = "dev"
CONFIG_NAME = "DEV"
# Debug settings
......
......@@ -3,6 +3,7 @@
# and overrides or adds to them.
from .base import *
TIER = "playground"
CONFIG_NAME = "USER TESTING"
# Debug settings
......
# Settings for a production GraceDB instance running in a container
from .base import *
TIER = "production"
DEBUG = False
# Turn on alerts
......
# Settings for a test/dev GraceDB instance running in a container
from .base import *
TIER = "test"
CONFIG_NAME = "TEST"
# Debug settings
......
......@@ -4,6 +4,7 @@
import socket
from .base import *
TIER = "dev"
CONFIG_NAME = "DEV"
# Debug settings
......
......@@ -3,6 +3,7 @@
# from base.py settings) and overrides or adds to them.
from .base import *
TIER = "playground"
CONFIG_NAME = "USER TESTING"
# Debug settings
......
......@@ -3,6 +3,7 @@
# settings) and overrides or adds to them.
from .base import *
TIER = "production"
DEBUG = False
# LVAlert Overseer settings
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment