Clean and backupable on-premise deployment of Sentry using Docker COmpose
550ba03435
8.12 was released on 2016-01-02 |
||
---|---|---|
.dockerignore | ||
.gitignore | ||
config.yml | ||
docker-compose.yml | ||
Dockerfile | ||
Makefile | ||
README.md | ||
requirements.txt | ||
sentry.conf.py |
Sentry On-Premise
Official bootstrap for running your own Sentry with Docker.
Requirements
- Docker 1.10.0+
- Compose 1.6.0+ (optional)
Up and Running
Assuming you've just cloned this repository, the following steps will get you up and running in no time!
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 todocker-compose.yml
inbase
asSENTRY_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.
Securing Sentry with SSL/TLS
If you'd like to protect your Sentry install with SSL/TLS, there are fantastic SSL/TLS proxies like HAProxy and Nginx.
Resources
- Documentation
- Bug Tracker
- Forums
- IRC (chat.freenode.net, #sentry)