taler-docs

commit ede1a143dd0ad3ad6ae71ca4d723f4f8a4842563
parent 9ed9003e81f949de314506165d65efa840bee1f6
Author: Florian Dold <florian.dold@gmail.com>
Date:   Tue, 27 Sep 2016 17:02:32 +0200

instructions

Diffstat:
M
deployment.rst
 | 
12
++++++++++--

1 file changed, 10 insertions(+), 2 deletions(-)
diff --git 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.