Indicate more clearly that docker-compose is just a guideline
Fixes #5 #9 #15 #19
This commit is contained in:
parent
8186ee21e8
commit
177ed0efa8
@ -9,9 +9,11 @@ Official bootstrap for running your own [Sentry](https://sentry.io/) with [Docke
|
||||
|
||||
## Up and Running
|
||||
|
||||
Assuming you've just cloned this repository, the following steps
|
||||
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. `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.
|
||||
@ -27,7 +29,7 @@ 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](http://www.haproxy.org/)
|
||||
fantastic SSL/TLS proxies like [HAProxy](http://www.haproxy.org/)
|
||||
and [Nginx](http://nginx.org/).
|
||||
|
||||
## Resources
|
||||
|
@ -1,3 +1,8 @@
|
||||
# NOTE: This docker-compose.yml is meant to be just an example of how
|
||||
# you could accomplish this on your own. It is not intended to work in
|
||||
# all use-cases and must be adapted to fit your needs. This is merely
|
||||
# a guideline.
|
||||
|
||||
# See docs.getsentry.com/on-premise/server/ for full
|
||||
# instructions
|
||||
|
||||
|
Reference in New Issue
Block a user