2
0
Clean and backupable on-premise deployment of Sentry using Docker COmpose
This repository has been archived on 2020-07-19. You can view files and clone it, but cannot push or open issues or pull requests.
Go to file
Matt Robenolt 9f52169bf9 Merge pull request #16 from JeanFred/upgrade-to-8-10
Upgrade to use sentry 8.10
2016-11-04 09:05:22 -07:00
.dockerignore mv docker-compose.yml{.example,} 2016-05-27 17:01:34 -07:00
.gitignore Mount the required volume 2016-05-27 16:45:18 -07:00
config.yml Update with 8.4 2016-05-26 16:07:32 -07:00
docker-compose.yml Compartmentalize data folder 2016-08-04 17:50:24 +03:00
Dockerfile Upgrade to use sentry 8.10 2016-11-04 15:43:27 +00:00
Makefile Default make all to build and push 2016-06-03 14:54:36 -07:00
README.md nginx.org no com 2016-10-15 00:35:53 -04:00
requirements.txt Getting started 2016-02-11 13:52:19 -08:00
sentry.conf.py Update with 8.4 2016-05-26 16:07:32 -07:00

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!

  1. 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!
  2. 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.
  3. docker-compose run --rm web upgrade - Build the database. Use the interactive prompts to create a user account.
  4. docker-compose up -d - Lift all services (detached/background mode).
  5. 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