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

[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 572251e  demo deployment guide
572251e is described below

commit 572251e5cfd38354d2d4fd0854f7c83bda0dab04
Author: MS <ms@taler.net>
AuthorDate: Sat Nov 12 11:31:07 2022 +0100

    demo deployment guide
---
 taler-developer-manual.rst | 19 ++++++++-----------
 1 file changed, 8 insertions(+), 11 deletions(-)

diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst
index 7d729c1..5608cb8 100644
--- a/taler-developer-manual.rst
+++ b/taler-developer-manual.rst
@@ -284,29 +284,26 @@ serve Taler on the Internet:
 -  ``taler-internal``: serves ``*.int.taler.net``, and does *NOT* get
    automatically built.
 
-The following two users are *never* automatically built, and they both
-serve ``*.demo.taler.net``. At any given time, only one is active and
-serves the HTTP requests from the outside; the other one can so be
-compiled without any downtime. If the compilation succeeds, the inactive
-user can be switched to become active (see next section), and vice versa.
-
--  ``demo-blue``
--  ``demo-green``
+- ``demo``: serves ``*.demo.taler.net``.  Never automatically built.
 
 
 Demo Upgrade Procedure
 ======================
 
+#. Login as the ``demo`` user on ``gv.taler.net``.
+#. Pull the latest ``deployment.git`` code.
+#.  Navigate to the ``deployment.git/docker/demo`` directory.
+#.  The README file is the reference about building and running the services.
+
 Upgrading the ``demo`` environment should be done with care, and ideally be
 coordinated on the mailing list before.  It is our goal for ``demo`` to always
 run a "working version" that is compatible with various published wallets.
 
-Before deploying on ``demo``, the same version of all components **must**
-be deployed *and* tested on ``int``.
-
 Please use the :doc:`demo upgrade checklist <checklist-demo-upgrade>` to make
 sure everything is working.
 
+Nginx is already configured to reach the services as exported by
+Docker Compose.
 
 Tagging components
 ------------------

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