Clean and backupable on-premise deployment of Sentry using Docker COmpose
ceed39c1d2
Remove a match-all glob pattern. It looks like some non-git tools read the `*,cover` as `*` and `cover` separately and basically ignore all files. Even though this is not really a problem with the repo itself, I think the change is still valid, considering `*,cover` looks like an invalid rule anyway. _____ Background: (__This part is vim-specific__) For a while now, my Neosnippet configuration has been going for a toss when working on our fork based off of this repo. I see a message similar to the one reported [here](https://github.com/Shougo/neocomplcache.vim/issues/468), but my vimrc configuration is as per the documentation available in the plugin docs. I finally spent enough time to debug this today, and it turns out this issue was happening *only* in this repo and nowhere else. So I went through the files that might've to do anything with folder-specific configuration (think dotenv, editorconfig etc.), and turned out `.gitignore` was the only such file; I use [this plugin](https://github.com/vim-scripts/gitignore) to load the gitignore rules into the `wildmenu` completion and the `*,` part basically (from what I understand) removes most of the load path configuration from vim 😄. I'll probably have to go make a change in that plugin as well though. |
||
|---|---|---|
| .dockerignore | ||
| .env.example | ||
| .gitignore | ||
| config.yml | ||
| docker-compose.yml | ||
| Dockerfile | ||
| LICENSE | ||
| 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)
Minimum Hardware Requirements:
- You need at least 3GB Ram
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.
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.cp -n .env.example .env- create env config filedocker-compose build- Build and tag the Docker servicesdocker-compose run --rm web config generate-secret-key- Generate a secret key. Add it to.envasSENTRY_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!
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 --pull # Build the services again after updating, and make sure we're up to date on patch version
docker-compose run --rm web upgrade # Run new migrations
docker-compose up -d # Recreate the services
Resources
- Documentation
- Bug Tracker
- Forums
- IRC (chat.freenode.net, #sentry)