The Django back-end for Tagging Tracker.
Clone or download
fredlawl Update requirements.txt based off github suggestions (#56) (#57)
Github notified the project team of insecure dependencies found in
requirements.txt. Update these dependencies to make the project secure again.

No functional change intended.

Signed-off-by: Frederick Lawler <>
Latest commit b2a86f2 Nov 19, 2018

Tagging Tracker Backend Services

These are the services that are powering the Tagging Tracker Application.

  • Note: * To use the existing Azure and auth0 accounts that are applied to this code, you need to contact one of the developers on the team. Otherwise, you'll need to setup your own Azure account and auth0 instance to run this code.

Getting Started

In order to checkout the code, and run it locally, the following steps are needed.

  1. You first need to generate your own self signed certificate pointing to the localhost domain. If you have any existing ones, feel free to use them as well. When creating them, you need to ensure that the file names coorelate to ~/.ssh/tagging_tracker/fullchain.pem (certificate file) and ~/.ssh/tagging_tracker/privkey.pem (private key).

    If you need assistance, I recommend this following article. Concentrate on the * Generate a Self-Signed Certificate section. *

  2. Checkout the repository

    git clone
  3. Once your certificate is generated and the repo is cloned, create a local.env file in the project directory. It should contain the following variables

    DEBUG - Whether the application is in debug mode. Defaults to False.
    SECRET_KEY - The secret key of the application. You can generate one here.
    DEPLOYED_URL - The URL of where the application is hosted at. This isn't need if you are running locally on your device.
    LOADBALANCER_URL - The URL of the loadbalancer for the application. This isn't needed if you are running locally on your device.
    DB_NAME - Name of the database. See below for running it locally.
    DB_USER - Name of the database user. See below for running it locally.
    DB_HOST - Host of the database. See below for running it locally.
    DB_PORT - Database port. See below for running it locally.
    DB_PASSWORD - Database Password. See below for running it locally.
    SSL_MODE - The SSL mode of the database connection. Defaults to disable.
    SSL_ROOT_CERT - The path of the SSL certificate. Defaults to empty string, and not used if SSL is disabled.
    AUTH0_CLIENTID - ClientID of the auth0 authentication engine.
    AUTH0_SECRET - Secret of the auth0 authentication engine.
    LOG_LEVEL - Error/Reporting logging level. More information here

    To get you started and running locally, here is a local.env file you can use.

    SECRET_KEY=<Your generated key>
    AUTH0_CLIENTID=<Create your own auth0 or ask developers for it>
    AUTH0_SECRET=<Create your own auth0 or ask developers for it>
  4. Optionally, configure your own settings by creating a docker-compose.override.yml file. See Docker Compose for a list of additional settings.

    NOTE: To configure ports properly, docker-compose.override.yml must contain all settings from the docker-compose.yml. Refer to this for more details. To run, use docker-compose -f docker-compose.override.yml up

  5. After the following previous steps are setup, running the following command to run the application.

    docker-compose up --build

    Anytime you change application code, kill the current container, and re run docker-compose up --build.


Read the Contribution Guide