This is for easy programmatic access to the tier name.

Alexander Pace authored 5 years ago and Alexander Pace committed 5 years ago

This is mostly just setting changes, bla bla bla

if the 'is_exposed' boolean is 'True', then the superevent is
public. changing the response so that it's 'is_public' would
require more than a two-line change.

These settings were previously handled in settings/container/production.py,
but we want to do some testing and I don't see any issues with having
them in the base container settings (settings/container/base.py).

Not feasible to use multiple DBs for read or write operations at
present. We're going to have to revisit this at some point. We leave
most of the code in place but commented out.

Not working as expected, so we are going to have to revisit this
feature in the near future.

These environment variables are now required.  Previously, the
corresponding Django settings would default to 'gracedb'.

Non-priority production containers will use the master for
writes and a read-replica database for reads. This commit adds
functionality for getting the replica's information from
environment variables and sets up a database routing scheme.

Containerized versions of the service will now get their LVAlert
credentials from the environment.  Also add a script for
processing environment variables and starting LVAlert overseer.

Settings have been reorganized and how different parameters are
determined has been reworked to be compatible with both a Puppet-based
VM deployment and a containerized deployment