[GNUnet-SVN] [taler-deployment] branch master updated: warn about db init

[gnunet]

This is an automated email from the git hooks/post-receive script.

marcello pushed a commit to branch master
in repository deployment.

The following commit(s) were added to refs/heads/master by this push:
     new b8f2b4f  warn about db init
b8f2b4f is described below

commit b8f2b4f7581746599295af51d8fd4475953166e8
Author: Marcello Stanisci <address@hidden>
AuthorDate: Mon Jun 10 14:38:00 2019 +0200

    warn about db init
---
 doc/onboarding.texi | 221 ++++++++++++++++++++++++++++------------------------
 1 file changed, 120 insertions(+), 101 deletions(-)

diff --git a/doc/onboarding.texi b/doc/onboarding.texi
index 686663f..cde5843 100644
--- a/doc/onboarding.texi
+++ b/doc/onboarding.texi
@@ -50,8 +50,8 @@ Texts.  A copy of the license is included in the section 
entitled
 @end ifnottex
 
 @menu
-* Standalone deployment::               Deploy Taler in your homepage @ 
taler.net
 * demo/test deployment::                Deploy Taler for "demo" and "test" 
setups.
+* Standalone deployment::               Deploy Taler in your homepage @ 
taler.net
 * Testing components::                  How to make and run tests
 * Releases::                            Releases patterns
 * Code::                                Where to find Taler code
@@ -60,6 +60,125 @@ Texts.  A copy of the license is included in the section 
entitled
 * Code coverage::                       Where to find coverage reports
 @end menu
 
+@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
+
+@cartouche
+@quotation Note
+If the DB schema of merchant or exchange changed, at this point
+it MIGHT be necessary to reset all the tables.  To this regard,
+consider running one of the following commands:
+
+@example
+# To reset the merchant DB.
+$ taler-merchant-dbinit -r
+
+# To reset the exchange DB.
+$ taler-exchange-dbinit -r
+@end example
+
+@end quotation
+@end cartouche
+
+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 Standalone deployment
 @chapter Standalone deployment
 
@@ -192,106 +311,6 @@ $ 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
 

-- 
To stop receiving notification emails like this one, please contact
address@hidden.