Run update.sh

This commit is contained in:
Docker Library Bot 2016-03-01 13:16:35 -08:00
parent 901c86b499
commit ef6a4cd156
3 changed files with 9 additions and 9 deletions

View File

@ -35,8 +35,8 @@ For more examples and ideas, visit:
$ docker images hello-world
REPOSITORY TAG IMAGE ID SIZE
hello-world latest 690ed74de00f 960 B
REPOSITORY TAG IMAGE ID VIRTUAL SIZE
hello-world latest 0a6ba66e537a 960 B
```
![logo](https://raw.githubusercontent.com/docker-library/docs/01c12653951b2fe592c1f93a13b4e289ada0e3a1/hello-world/logo.png)

View File

@ -25,8 +25,8 @@ For more examples and ideas, visit:
$ docker images hello-world
REPOSITORY TAG IMAGE ID SIZE
hello-world latest 690ed74de00f 960 B
REPOSITORY TAG IMAGE ID VIRTUAL SIZE
hello-world latest 0a6ba66e537a 960 B
```
%%LOGO%%

View File

@ -45,7 +45,7 @@ Sentry is a realtime event logging and aggregation platform. It specializes in m
4. If this is a new database, you'll need to run `upgrade`
```console
$ docker run -it --rm -e SENTRY_SECRET_KEY <secret-key> --link sentry-postgres:postgres --link sentry-redis:redis sentry upgrade
$ docker run -it --rm -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-postgres:postgres --link sentry-redis:redis sentry upgrade
```
**Note: the `-it` is important as the initial upgrade will prompt to create an initial user and will fail without it**
@ -53,14 +53,14 @@ Sentry is a realtime event logging and aggregation platform. It specializes in m
5. Now start up Sentry server
```console
$ docker run -d --name my-sentry -e SENTRY_SECRET_KEY <secret-key> --link sentry-redis:redis --link sentry-postgres:postgres sentry
$ docker run -d --name my-sentry -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-redis:redis --link sentry-postgres:postgres sentry
```
6. The default config needs a celery beat and celery workers, start as many workers as you need (each with a unique name)
```console
$ docker run -d --name sentry-celery-beat -e SENTRY_SECRET_KEY <secret-key> --link sentry-postgres:postgres --link sentry-redis:redis sentry celery beat
$ docker run -d --name sentry-celery1 -e SENTRY_SECRET_KEY <secret-key> --link sentry-postgres:postgres --link sentry-redis:redis sentry celery worker
$ docker run -d --name sentry-celery-beat -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-postgres:postgres --link sentry-redis:redis sentry celery beat
$ docker run -d --name sentry-celery1 -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-postgres:postgres --link sentry-redis:redis sentry celery worker
```
### Port mapping
@ -72,7 +72,7 @@ If you'd like to be able to access the instance from the host without the contai
If you did not create a superuser during `upgrade`, use the following to create one:
```console
$ docker run -it --rm -e SENTRY_SECRET_KEY <secret-key> --link sentry-redis:redis --link sentry-postgres:postgres sentry createuser
$ docker run -it --rm -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-redis:redis --link sentry-postgres:postgres sentry createuser
```
## Environment variables