ansible-taler-exchange

Ansible playbook to deploy a production Taler Exchange
Log | Files | Refs | Submodules | README | LICENSE

commit 3e9cef01e61115643087fa140e424978caad3d1d
parent 243c7b80dad23515c814cf2eb308fbe1024ceb7e
Author: Devan Carpenter <devan@taler.net>
Date:   Mon, 18 Nov 2024 15:58:57 +0000

update README

Diffstat:
MREADME | 42+++++++++++++++---------------------------
1 file changed, 15 insertions(+), 27 deletions(-)

diff --git a/README b/README @@ -1,32 +1,20 @@ -RUN THE ANSIBLE SETUP -======================== +Running the Playbook +==================== -To run this ansible deployment script simply run : +To run the main playbook (playbooks/setup.yml): --------------------------------------------------- +``` +$ ansible-playbook --verbose -i <host>, --user root playbooks/setup.yml +``` -1.For staging and tests: ansible-playbook -i inventories/staging --user root playbooks/play.yml -2.For production: ansible-playbook -i inventories/production --user root playbooks/play.yml - -Roles (set of tasks): -=========================== - -Brief explanation about what the play.yml really executes: - -Roles: - -0.Packages (including Taler packages) -1.Webserver -2.Database -3.Taler setup - -ROLE-> TASKS: ---------------- -Packages: Install base packges + Add Taler repo to sources.list + Install Taler packages (exchange so far) -Webserver: Install NGINX + Enable Virtualhost + Request CERTS -Database: Install Postgres + Configure Postgres -Taler: Taler specific configurations (as setup-exchange.sh from regional currency script (old Netzbon)). - - - +Instead of specifying the host(s) as arguments (note the trailing comma!) +you can pass an inventory file. See `inventories/`, and update accordingly. +Testing Locally +=============== +With podman and ansible installed locally one can run `./test.sh`. +This will begin building the Containerfile in this repo, which is a Debian +base with systemd and a paswordless ssh server configured. Then container +will start, binding port 8022 to 127.0.0.1 on the host. Finally +the setup playbook will be run on the container via ssh.