diff options
Diffstat (limited to 'libeufin/regional-automated-manual.rst')
| -rw-r--r-- | libeufin/regional-automated-manual.rst | 76 |
1 files changed, 22 insertions, 54 deletions
diff --git a/libeufin/regional-automated-manual.rst b/libeufin/regional-automated-manual.rst index b199aa92..645e000f 100644 --- a/libeufin/regional-automated-manual.rst +++ b/libeufin/regional-automated-manual.rst @@ -105,8 +105,8 @@ The script will start by installing the required packages and then asking you fu #. Whether to use TLS or not. You should answer ``y`` in most cases. #. Whether to setup SMS two-factor authentication using `Telesign <https://www.telesign.com>`_, multi-factor authentication is strongly recommended, especially when regional currency can be converted to fiat currency. This requires `a Customer ID and an API Key <https://developer.telesign.com/enterprise/docs/authentication#basic-authentication>`_. You should answer ``y`` in most cases. #. The admin password for the bank. Be absolutely sure to enter a very, very long and high-entropy password, preferably using the autogenerated one. -#. Whether to generate terms of service (ToS) for the exchange from default templates. -#. Whether to generate a privacy policy for the exchange from default templates. +#. Whether to generate terms of service (ToS) for the exchange from default templates. +#. Whether to generate a privacy policy for the exchange from default templates. The information you entered as well as the generated bank admin password will be stored in a file called ``config/user.conf``. If you run the script in @@ -230,62 +230,30 @@ The EBICS setup is finished once the bank keys have been accepted. Configuring the Exchange for Conversion +++++++++++++++++++++++++++++++++++++++ -By default, the exchange is setup to perform conversion without any restrictions. You may configure restrictions on the bank accounts that may originate the funds, for example, to prevent international wire transfers that may expose you to additional compliance risks: +In our automated setup the second account is automatically set up correctly +without fees or special restrictions. However, various additional +*restrictions* and *options* could be configured. Details are explained in +the :ref:`regional conversion setup <regional-conversion-setup>` section for the +manual setup and in the the manpage of ``taler-exchange-offline``. -.. code-block:: console - - # Make sure environment variables are available - $ source config/user.conf - - $ sudo -u taler-exchange-offline taler-exchange-offline \ - enable-account \ - "${CONVERSION_PAYTO}" \ - conversion-url "${PROTO}://bank.$DOMAIN_NAME/conversion-info/" \ - # restrictions ... - upload - -.. note:: - Refer to the manpage ``taler-exchange-offline`` for a full array of possible restrictions. - -System ON! -++++++++++ - -The last step is to enable libeufin-nexus to :ref:`import incoming bank -transactions <receive-transaction-data>` (cash in) and to :ref:`trigger -outgoing bank transactions <sending-payments>` (cash out). - -.. code-block:: console - - # systemctl enable --now libeufin-nexus.target - -Configuring exchange terms -++++++++++++++++++++++++++ - -You can use your own terms of service and privacy policy. You can use the default templates in ``/usr/share/taler/terms`` as a guide. -Assuming you have custom terms of service and privacy policy ``rst`` teamplte files at ``TOS_PATH`` and ``PRIVACY_PATH``, the following commands generate the terms files: -.. code-block:: console - - # taler-terms-generator -i "$TOS_PATH" - # taler-terms-generator -i "$PRIVACY_PATH" - -You now have to specify the terms file names in the exchange config: - -.. code-block:: console - - # TERMS_ETAG="$(basename "$TOS_PATH" .rst)" - # PRIVACY_ETAG="$(basename "$PRIVACY_PATH" .rst)" +.. include:: ../frags/regional-system-on.rst +.. include:: ../frags/deploying-tos.rst +.. include:: ../frags/regional-manual-use.rst -.. code-block:: ini - [exchange] - TERMS_ETAG=${TERMS_ETAG} - PRIVACY_ETAG=${PRIVACY_ETAG} +Installing Updates +++++++++++++++++++ -Make sure to restart taler-exchange after changing these configuration options: +The standard procedure for installing updates is to: -.. code-block:: console + * First, make a backup (!) + * Stop Taler services + * Install new version + * Upgrade databases + * Start Taler services - # systemctl restart taler-exchange.target - -.. include:: ../frags/regional-manual-use.rst +The "upgrade.sh" script in the "regional-currency/" folder of "deployment.git" +shows how to do the above steps *except* for the backup. For the backup, all +critical bits of data will be in the Postgresql databases. Thus, we recommend +following the database manual on making backups. |