kmlabz/sentry-onpremise
kmlabz/sentry-onpremise
Archived
2
0
Fork 0
Code Pull Requests Releases Activity
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.
3745dc4fe1
sentry-onpremise/README.md
eritikass e21d9a3972 Improve setup (#123) 
* declare sentry volumes external

* move SENTRY_SECRET_KEY to .env file (not in git repo)

* ignore docker-compose.override.yml to allow extending
2018-10-17 10:02:22 -07:00

2.1 KiB
Raw Blame History

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.

  1. docker volume create --name=sentry-data && docker volume create --name=sentry-postgres - Make our local database and sentry volumes Docker volumes have to be created manually, as they are declared as external to be more durable.
  2. cp -n .env.example .env - create env config file
  3. docker-compose build - Build and tag the Docker services
  4. docker-compose run --rm web config generate-secret-key - Generate a secret key. Add it to .env as SENTRY_SECRET_KEY.
  5. docker-compose run --rm web upgrade - Build the database. Use the interactive prompts to create a user account.
  6. docker-compose up -d - Lift all services (detached/background mode).
  7. Access your instance at localhost:9000!

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.

Updating Sentry

Updating Sentry using Compose is relatively simple. Just use the following steps to update. Make sure that you have the latest version set in your Dockerfile. Or use the latest version of this repository.

Use the following steps after updating this repository or your Dockerfile:

docker-compose build # Build the services again after updating
docker-compose run --rm web upgrade # Run new migrations
docker-compose up -d # Recreate the services

Resources