starred/stf
1
0
Fork 0
mirror of https://github.com/DeviceFarmer/stf.git synced 2026-04-21 16:25:13 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix inconsistent RethinkDB version in deployment docs. Fixes #385.

Browse Source
This commit is contained in:
Simo Kinnunen
2016-08-02 16:34:51 +09:00
committed by GitHub
parent d104e94083
commit 9e5f8ca5f8
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/DEPLOYMENT.md
View File

@@ -107,7 +107,7 @@ If you need to expand your RethinkDB cluster beyond one server you may encounter
You will also have to:
1. Modify the `--cache-size` as you please. It limits the amount of memory RethinkDB uses and is given in megabytes, but is not an absolute limit! Real usage can be slightly higher.
2. Update the version number in `rethinkdb:2.1.1` for the latest release. We don't use `rethinkdb:latest` here because then you might occasionally have to manually rebuild your indexes after an update and not even realize it, bringing the whole system effectively down.
2. Update the version number in `rethinkdb:2.3` for the latest release. We don't use `rethinkdb:latest` here because then you might occasionally have to manually rebuild your indexes after an update and not even realize it, bringing the whole system effectively down.
3. The `AUTHKEY` environment variable is only for convenience when linking. So, the first time you set things up, you will have to access http://DB_SERVER_IP:8080 after starting the unit and run the following command:
```javascript
@@ -138,7 +138,7 @@ ExecStart=/usr/bin/docker run --rm \
-v /srv/rethinkdb:/data \
-e "AUTHKEY=YOUR_RETHINKDB_AUTH_KEY_HERE_IF_ANY" \
--net host \
rethinkdb:2.1.5 \
rethinkdb:2.3 \
rethinkdb --bind all \
--cache-size 8192
ExecStop=-/usr/bin/docker stop -t 10 %p