#5760

1 files changed, 101 insertions, 12 deletions

diff --git a/doc/onboarding.texi b/doc/onboarding.texi
index 040eba5..686663f 100644
--- a/doc/onboarding.texi
+++ b/doc/onboarding.texi
@@ -51,13 +51,13 @@ Texts.  A copy of the license is included in the section entitled
 
 @menu
 * Standalone deployment::               Deploy Taler in your homepage @ taler.net
+* demo/test deployment::                Deploy Taler for "demo" and "test" setups.
 * Testing components::                  How to make and run tests
 * Releases::                            Releases patterns
 * Code::                                Where to find Taler code
 * Bugtracking::                         How to track Taler bugs
 * Continuous integration::              How CI is currently performed
 * Code coverage::                       Where to find coverage reports
-* Demo and Test::                       Live Taler services
 @end menu
 
 @node Standalone deployment
@@ -192,6 +192,106 @@ $ taler-deployment-start
 All the services should be reachable at the following URL:
 @code{https://env.taler.net/<username>/<service>[/endopoint[?arg0=x&arg1=y]]}
 
+@node demo/test deployment
+@chapter demo/test deployment
+
+The following steps are valid if run as one of the following users:
+
+@itemize
+@item demo-blue
+@item demo-green
+@item test-blue
+@item test-green
+@end itemize
+
+@section Compile and switch color.
+
+If the setup is already bootstrapped, then it should only be needed
+to login as 'demo-X' (with X being the inactive color); and then:
+
+@example
+$ source activate
+$ taler-deployment-build
+@end example
+
+and then switch the color by logging in as the @emph{demo} user,
+and switch the color with the following command:
+
+@example
+$ taler-deployment-switch-demo-X
+@end example
+
+@section Full bootstrap.
+
+In order to bootstrap a Taler installation under a empty home
+directory, do:
+
+@example
+$ cd $HOME 
+$ git clone git://git.taler.net/deployment
+@end example
+
+Then run the bootstrap script that
+will download all the repositories.
+
+@example
+$ ./deployment/bootstrap-bluegreen demo X # with X == 'green' / 'blue'
+@end example
+
+If successful, then activate the new environment with:
+
+@example
+source activate
+@end example
+
+Compile and install all the components.
+@example
+$ taler-deployment-build
+@end example
+
+Create the global configuration file.
+
+@example
+$ taler-deployment-config-generate
+@end example
+
+Create the folder to share data between the two colors.
+
+@example
+$ taler-deployment-hier
+@end example
+
+Create all the keys.
+
+@example
+$ taler-deployment-keyup
+@end example
+
+Sign the @code{/wire} response for the exchange.
+
+@example
+$ taler-deployment-sign
+@end example
+
+If all the steps succeeded, then it should be possible
+to launch all the services.  Give:
+
+@example
+$ taler-deployment-start
+@end example
+
+Verify that all services are up and running:
+@example
+$ taler-deployment-arm -I
+$ tail logs/<component>-<date>.log
+@end example
+
+Switch now to the color just built:
+
+@example
+$ taler-deployment-switch-<demo/test>-<blue/green>
+@end example
+
 @node Testing components
 @chapter Testing components
 
@@ -391,15 +491,4 @@ Code coverage is done with the Gcov / Lcov (http://ltp.sourceforge.net/coverage/
 combo, and it is run *nightly* (once a day) by a Buildbot worker.  The
 coverage results are then published at @code{https://lcov.wild.gv.taler.net/}.
 
-@node Demo and Test
-@chapter Demo and Test
-Taler code is normally kept under two Git branches: @code{master} and @code{stable}.
-The first branch keeps the latest code, therefore more experimental and
-unstable.  The latter branch is usually pointing at the latest release and
-is expected to be more stable.
-
-Finally, there exist two live systems that run Taler from those two
-branches, and where any user can try the Taler experience.  The 'master'
-branch is run at @code{https://test.wild.gv.taler.net/} and 'stable' at
-@code{https://demo.wild.gv.taler.net/}.
 @bye