[taler-docs] branch master updated: remove obsolete

[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 4b58d81  remove obsolete
4b58d81 is described below

commit 4b58d81adf3d4067d0d5a1e7856ab20ac54a0cf7
Author: MS <ms@taler.net>
AuthorDate: Tue Nov 8 16:07:55 2022 +0100

    remove obsolete
---
 taler-developer-manual.rst | 94 ----------------------------------------------
 1 file changed, 94 deletions(-)

diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst
index 09f38b8..7d729c1 100644
--- a/taler-developer-manual.rst
+++ b/taler-developer-manual.rst
@@ -323,100 +323,6 @@ All Taler components must be tagged with git before they 
are deployed on the
   SS = serial
 
 
-Environment Layout
-------------------
-
-Environments have the following layout:
-
-.. code-block:: none
-
-  $HOME/
-    deployment (deployment.git checkout)
-    envcfg.py  (configuration of the Taler environment)
-    activate   (bash file, sourced to set environment variables)
-    logs/      (log files)
-    local/     (locally installed software)
-    sources/   (sources repos of locally build components)
-    sockets/   (unix domain sockets of running components)
-    taler-data (on-disk state, public and private keys)
-    .config/taler.conf (main Taler configuration file)
-
-On ``demo-blue`` and ``demo-green``, ``taler-data`` is a symlink pointing to 
``$HOME/demo/shared-data``
-instead of a directory.
-
-
-Using envcfg.py
----------------
-
-The ``$HOME/envcfg.py`` file contains (1) the name of the environment and (2) 
the version
-of all components we build (in the form of a git rev).
-
-The ``envcfg.py`` for demo looks like this:
-
-.. code-block:: python
-
-  env = "demo"
-  tag = "demo-2019-10-05-01:
-  tag_gnunet = tag
-  tag_libmicrohttpd = tag
-  tag_exchange = tag
-  tag_merchant = tag
-  tag_bank = tag
-  tag_twister = tag
-  tag_landing = tag
-  tag_donations = tag
-  tag_blog = tag
-  tag_survey = tag
-  tag_backoffice = tag
-  tag_sync = tag
-
-Currently only the variables ``env`` and ``tag_${component}`` are used.
-
-When deploying to ``demo``, the ``envcfg.py`` should be committed to 
``deployment.git/envcfg/envcfg-demo-YYYY-MM-DD-SS.py``.
-
-
-Bootstrapping an Environment
-----------------------------
-
-.. code-block:: console
-
-  $ git clone https://git.taler.net/deployment.git ~/deployment
-  $ cp ~/deployment/envcfg/$ENVCFGFILE ~/envcfg.py
-  $ ./deployment/bin/taler-deployment bootstrap
-  $ source ~/activate
-  $ taler-deployment build
-  $ taler-deployment-prepare
-  $ taler-deployment-start
-  $ taler-deployment-arm -I # check everything works
-  # The following command sets up the 'blog' and 'donations' instances.
-  $ taler-config-instances
-
-
-Upgrading an Existing Environment
----------------------------------
-
-.. code-block:: console
-
-  $ rm -rf ~/sources ~/local
-  $ git -C ~/deployment pull
-  $ cp ~/deployment/envcfg/$ENVCFGFILE ~/envcfg.py
-  $ taler-deployment bootstrap
-  $ taler-deployment build
-  $ taler-deployment-prepare
-  $ taler-deployment-restart
-  $ taler-deployment-arm -I # check everything works
-
-Switching Demo Colors
----------------------
-
-As the ``demo`` user, to switch to color ``${COLOR}``,
-run the following script from ``deployment/bin``:
-
-.. code-block:: console
-
-   $ taler-deployment switch-demo
-
-
 Environments and Builders on taler.net
 ======================================
 

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