Browse code
Add SERVICE_TOKEN to the sample local.conf
I expect the sample local.conf file to contain all the required
variables. However, after copying samples/local.conf, the stack.sh
script still asks for SERVICE_TOKEN.
This commit adds the SERVICE_TOKEN definition to local.conf so that a
new user can just copy samples/local.conf, edit it, and have a running
stack.sh without the mild annoyance of having more variables to set.
Change-Id: Ifb163c7f67c80037d8b10458f2df458a20da4667
Georges Dubus authored on 2014/07/22 18:45:03Showing 1 changed files
| ... | ... |
@@ -24,8 +24,10 @@ |
| 24 | 24 |
# While ``stack.sh`` is happy to run without ``localrc``, devlife is better when |
| 25 | 25 |
# there are a few minimal variables set: |
| 26 | 26 |
|
| 27 |
-# If the ``*_PASSWORD`` variables are not set here you will be prompted to enter |
|
| 28 |
-# values for them by ``stack.sh`` and they will be added to ``local.conf``. |
|
| 27 |
+# If the ``SERVICE_TOKEN`` and ``*_PASSWORD`` variables are not set |
|
| 28 |
+# here you will be prompted to enter values for them by ``stack.sh`` |
|
| 29 |
+# and they will be added to ``local.conf``. |
|
| 30 |
+SERVICE_TOKEN=azertytoken |
|
| 29 | 31 |
ADMIN_PASSWORD=nomoresecrete |
| 30 | 32 |
MYSQL_PASSWORD=stackdb |
| 31 | 33 |
RABBIT_PASSWORD=stackqueue |