[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [taler-deployment] branch master updated: instructions on h
From: |
gnunet |
Subject: |
[GNUnet-SVN] [taler-deployment] branch master updated: instructions on how to run a database for a standalone setup |
Date: |
Tue, 26 Dec 2017 11:36:50 +0100 |
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 859feb3 instructions on how to run a database for a standalone setup
859feb3 is described below
commit 859feb37e1657a18367030207f2840cd7cf12e66
Author: Marcello Stanisci <address@hidden>
AuthorDate: Tue Dec 26 11:36:08 2017 +0100
instructions on how to run a database for a standalone setup
---
doc/onboarding.texi | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/doc/onboarding.texi b/doc/onboarding.texi
index c0ba2d9..ad12dff 100644
--- a/doc/onboarding.texi
+++ b/doc/onboarding.texi
@@ -342,7 +342,17 @@ $ source activate
# contain $HOME/local/bin.
$ echo $PATH
-# The actual compilation:
+# Then we need to install GNUnet beforehand, as it provides the 'ARM'
+# utility that is used to start the database service.
+$ cd deployment/taler-arm/
+$ make gnunet-stamp
+
+# Now we can start the database, with ($CWD is irrelevant now):
+$ taler-deployment-arm -s
+$ taler-deployment-arm -i taler-postgres-standalone
+
+# If the previous commands succeeded, then we can install all the remaining
+# components and run checks for them. Issue:
$ taler-deployment-build
@end example
--
To stop receiving notification emails like this one, please contact
address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [taler-deployment] branch master updated: instructions on how to run a database for a standalone setup,
gnunet <=