taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit c6337a2b100bacafd48a5ae33a04714d21578bd3
parent ba96b3a7628a25c1e17604fda6dc92e4df09d5f0
Author: Florian Dold <florian.dold@gmail.com>
Date:   Sat,  2 Nov 2019 14:49:48 +0100

demo upgrade process

Diffstat:
Mdevelopers-manual.rst | 22++++++++++++++++++----
1 file changed, 18 insertions(+), 4 deletions(-)

diff --git a/developers-manual.rst b/developers-manual.rst @@ -203,13 +203,13 @@ The ``envcfg.py`` for demo looks like this: Currently only the variables ``env`` and ``tag_${component}`` are used. -Bootstrapping an environment +Bootstrapping an Environment ---------------------------- .. code-block:: sh - $ cd $HOME - $ git clone https://git.taler.net/deployment.git + $ git clone https://git.taler.net/deployment.git ~/deployment + $ cp ~/deployment/envcfg.py.template ~/envcfg.py $ $EDITOR ~/envcfg.py $ ./deployment/bin/taler-deployment bootstrap $ source ~/activate @@ -219,7 +219,21 @@ Bootstrapping an environment $ taler-deployment-start -Switching demo colors +Upgrading an Existing Environment +--------------------------------- + +.. code-block:: sh + + $ rm -rf ~/sources ~/local + $ git -C ~/deployment pull + $ $EDITOR ~/envcfg.py + $ taler-deployment build + $ taler-deployment-keyup + $ taler-deployment-sign + $ taler-deployment-start + + +Switching Demo Colors --------------------- As the ``demo`` user, to switch to color ``${COLOR}``,