There may need to be modifications to the included docker-compose.yml file to accommodate your needs or your environment. These instructions are a guideline for what you should generally do.
mkdir -p data/{sentry,postgres} - Make our local database and sentry config directories. This directory is bind-mounted with postgres so you don't lose state!
docker-compose run --rm web config generate-secret-key - Generate a secret key. Add it to docker-compose.yml in base as SENTRY_SECRET_KEY.
docker-compose run --rm web upgrade - Build the database. Use the interactive prompts to create a user account.
docker-compose up -d - Lift all services (detached/background mode).
Access your instance at localhost:9000!
Note that as long as you have your database bind-mounted, you should be fine stopping and removing the containers without worry.
Production configuration
We can use this forked repo for use Sentry in a production environment in combination with Traefik.
Install Sentry On Premise in production with Docker and Traefik
We would like to install Sentry with the help of Traefik.
The default Sentry On Premise configuration of docker containers work with links, but we need to customise the configuration of networks to make it works with Traefik.
We can check out this Github repo that i've prepared:
The problem that i had with On Premise was related to communication between containers. Since i didn't figure out why it doesn't work, i found a trick that consist in run before the default configuration to make it install and work and then run the daton89/sentry-on-premise docker-compose file to make it works with Traefik proxy.
After you make changes in config.yml, you must remove existing sentry containers. And when you rerun docker-compose, it will build new images with updated config.
docker-compose stopdocker-compose downdocker imagesdocker rmi -f <image_ids>docker-compose up -d
`docker-compose stop && docker-compose down && rm -rf data/`
