diff options
| author | Florian Dold <florian.dold@gmail.com> | 2019-11-02 15:03:34 +0100 |
|---|---|---|
| committer | Florian Dold <florian.dold@gmail.com> | 2019-11-02 15:03:34 +0100 |
| commit | 9807576ea8c1a0e7a116cc138fd3ee7224822327 (patch) | |
| tree | f7acb77fd669b7c7d7065af503483aadd745538c | |
| parent | c6337a2b100bacafd48a5ae33a04714d21578bd3 (diff) | |
| download | docs-9807576ea8c1a0e7a116cc138fd3ee7224822327.tar.gz docs-9807576ea8c1a0e7a116cc138fd3ee7224822327.tar.bz2 docs-9807576ea8c1a0e7a116cc138fd3ee7224822327.zip | |
demo upgrade process
| -rw-r--r-- | developers-manual.rst | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/developers-manual.rst b/developers-manual.rst index ba642e43..1206135f 100644 --- a/developers-manual.rst +++ b/developers-manual.rst @@ -202,6 +202,8 @@ The ``envcfg.py`` for demo looks like this: 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 ---------------------------- @@ -209,8 +211,7 @@ Bootstrapping an Environment .. code-block:: sh $ git clone https://git.taler.net/deployment.git ~/deployment - $ cp ~/deployment/envcfg.py.template ~/envcfg.py - $ $EDITOR ~/envcfg.py + $ cp ~/deployment/envcfg/$ENVCFGFILE ~/envcfg.py $ ./deployment/bin/taler-deployment bootstrap $ source ~/activate $ taler-deployment build @@ -226,7 +227,8 @@ Upgrading an Existing Environment $ rm -rf ~/sources ~/local $ git -C ~/deployment pull - $ $EDITOR ~/envcfg.py + $ cp ~/deployment/envcfg/$ENVCFGFILE ~/envcfg.py + $ taler-deployment bootstrap $ taler-deployment build $ taler-deployment-keyup $ taler-deployment-sign |