Run update.sh
This commit is contained in:
parent
6f1e0968b9
commit
a63e19a721
|
|
@ -80,7 +80,7 @@ Documentation for this image is stored in the [`rethinkdb/` directory](https://g
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any problems with or questions about this image, please contact us through a [GitHub issue](https://github.com/stuartpb/rethinkdb-dockerfiles/issues). If the issue is related to a CVE, please check for [a `cve-tracker` issue on the `official-images` repository first](https://github.com/docker-library/official-images/issues?q=label%3Acve-tracker).
|
||||
If you have any problems with or questions about this image, please contact us through a [GitHub issue](https://github.com/rethinkdb/rethinkdb-dockerfiles/issues). If the issue is related to a CVE, please check for [a `cve-tracker` issue on the `official-images` repository first](https://github.com/docker-library/official-images/issues?q=label%3Acve-tracker).
|
||||
|
||||
You can also reach many of the official image maintainers via the `#docker-library` IRC channel on [Freenode](https://freenode.net).
|
||||
|
||||
|
|
@ -88,4 +88,4 @@ You can also reach many of the official image maintainers via the `#docker-libra
|
|||
|
||||
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
|
||||
|
||||
Before you start to code, we recommend discussing your plans through a [GitHub issue](https://github.com/stuartpb/rethinkdb-dockerfiles/issues), especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a [GitHub issue](https://github.com/rethinkdb/rethinkdb-dockerfiles/issues), especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.
|
||||
|
|
|
|||
|
|
@ -58,8 +58,8 @@ Sentry is a realtime event logging and aggregation platform. It specializes in m
|
|||
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-cron -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-postgres:postgres --link sentry-redis:redis sentry run cron
|
||||
$ docker run -d --name sentry-worker-1 -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-postgres:postgres --link sentry-redis:redis sentry run worker
|
||||
```
|
||||
|
||||
### Port mapping
|
||||
|
|
|
|||
Loading…
Reference in New Issue