summaryrefslogtreecommitdiff
path: root/deployment.rst
diff options
context:
space:
mode:
authorFlorian Dold <florian.dold@gmail.com>2016-09-27 17:02:32 +0200
committerFlorian Dold <florian.dold@gmail.com>2016-09-27 17:02:32 +0200
commitede1a143dd0ad3ad6ae71ca4d723f4f8a4842563 (patch)
tree468ed279e3947a338554c851283e631dd8cc14a9 /deployment.rst
parent9ed9003e81f949de314506165d65efa840bee1f6 (diff)
downloaddocs-ede1a143dd0ad3ad6ae71ca4d723f4f8a4842563.tar.gz
docs-ede1a143dd0ad3ad6ae71ca4d723f4f8a4842563.tar.bz2
docs-ede1a143dd0ad3ad6ae71ca4d723f4f8a4842563.zip
instructions
Diffstat (limited to 'deployment.rst')
-rw-r--r--deployment.rst12
1 files changed, 10 insertions, 2 deletions
diff --git a/deployment.rst b/deployment.rst
index 8ddd5b5c..6619c5eb 100644
--- a/deployment.rst
+++ b/deployment.rst
@@ -67,7 +67,7 @@ The following instructions wipe out the old deployment completely.
[...] sockets -> /home/demo-green/sockets/
In this case, `demo-green` is the active deployment, and `demo-blue` should be updated.
-After the update is over, the symlink will be pointed to `demo-blue`.
+After the update is over, the `/home/demo/sockets` symlink will be pointed to `demo-blue`.
.. code-block:: none
$ rm -rf $HOME
@@ -77,4 +77,12 @@ After the update is over, the symlink will be pointed to `demo-blue`.
# set environment appropriately
$ . activate
$ taler-deployment-build
- $
+
+ # upgrade the database! this
+ # process depends on the specific version
+
+ $ taler-deployment-start
+
+ # look at the logs, verify that everything is okay
+
+Now the symlink can be updated.