[taler-docs] branch master updated: demo-deployment instructions

[gnunet]

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

ms pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new e04fcc2  demo-deployment instructions
e04fcc2 is described below

commit e04fcc21a7417be7288f0bcabf466e73e873fe17
Author: MS <ms@taler.net>
AuthorDate: Thu Aug 25 09:34:29 2022 +0200

    demo-deployment instructions
---
 demo-deployment.rst | 44 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 44 insertions(+)

diff --git a/demo-deployment.rst b/demo-deployment.rst
new file mode 100644
index 0000000..820b7d0
--- /dev/null
+++ b/demo-deployment.rst
@@ -0,0 +1,44 @@
+This document explains how to install Taler+LibEuFin
+on gv.taler.net, for demo.taler.net.
+
+The installation uses deployment.git/bin/taler-gv, which
+offers the following subcommands:
+
+* bootstrap
+* build
+* prepare
+* launch
+* stop
+
+How to install
+--------------
+1. python3 taler-gv bootstrap
+2. python3 taler-gv build
+3. python3 taler-gv prepare
+
+If everything worked, then launch all the services
+with:
+
+4. python3 taler-gv launch
+
+Configuration files
+-------------------
+The 'prepare' subcommand generate all the configuration files
+and put them in $HOME/config.  NOTE: at this point, the Python
+demo sites are ignoring the '-c' flag and *still* accessing the
+config file at $HOME/.config/taler.conf, which is now a symlink
+to $HOME/config/taler.conf.
+
+Logging
+-------
+Logging files are placed into logs/, but _some_ logging may
+still be found through SystemD.
+
+Sources
+-------
+Downloaded by the 'bootstrap' subcommand into $HOME/sources.
+
+Process manager
+---------------
+SystemD is the process manager, invoked at prepare/launch/stop
+subcommands.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.