taler-deployment

Deployment scripts and configuration files
Log | Files | Refs | README

commit 9e49f67c16d3ffe4e23fae3671c8ae82212626e5
parent e0c9594e3a76b235e2db738ab95c96a4e45fcfda
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date:   Thu, 20 Jul 2017 15:05:42 +0200

Warn about lcov worker db.

Diffstat:
Mdoc/onboarding.texi | 14++++++++++++++
1 file changed, 14 insertions(+), 0 deletions(-)

diff --git a/doc/onboarding.texi b/doc/onboarding.texi @@ -183,6 +183,20 @@ $ taler-deployment-bbstart $ taler-deployment-bbstop @end example +@b{NOTE:} a Postgres "per-user" database service should always +be running, as @emph{lcovslave} is deployed in a standalone environment. + +Start the database service in the following way: + +@example +# Assuming you already sourced ~/activate +$ taler-deployment-arm -s +$ taler-deployment-arm -i taler-postgres-standalone +# Stop it this way: +$ taler-deployment-arm -k taler-postgres-standalone +# To stop 'arm', issue: +$ taler-deployment-arm -e +@end example @subsubsection Switcher worker