45078e6566
Previously, I had changed the default value to "", to force users to set the SECRET_KEY value (the app refuses to start if SECRET_KEY is empty). The problem with that is, out of the box, with the default configuration, the tests also don't run and complain about the empty SECRET_KEY. So, a compromise: revert back to the default value "---". At runtime, if SECRET_KEY has the default value, show a warning at the top of every page.
Running with Docker
This is a sample configuration for running Healthchecks with Docker and Docker Compose.
Note: The Docker configuration is a recent addition, and, for the time being, should be considered as highly experimental.
Note: For the sake of simplicity, the sample configuration starts a single database node and a single web server node, both on the same host. It also does not handle SSL termination. If you plan to expose it to the public internet, make sure you put a SSL-terminating load balancer or reverse proxy in front of it.
Getting Started
-
Add your configuration in the
/docker/.envfile. As a minimum, set the following fields:DEFAULT_FROM_EMAIL– the "From:" address for outbound emailsEMAIL_HOST– the SMTP serverEMAIL_HOST_PASSWORD– the SMTP passwordEMAIL_HOST_USER– the SMTP usernameSECRET_KEY– secures HTTP sessions, set to a random value
-
Create and start containers:
$ docker-compose up -
Create a superuser:
$ docker-compose run web /opt/healthchecks/manage.py createsuperuser -
Open http://localhost:8000 in your browser and log in with the credentials from the previous step.