taler-deployment

Deployment scripts and configuration files
Log | Files | Refs | README

README (2234B)


      1 Run with podman
      2 ---------------
      3 
      4 This folder contains scripts to be able to test the regional setup with podman
      5 
      6 Start by building the image with `build.sh` script, it will create an debian image named `taler` with the minimal software necessary to run all-in-one machine. The image is expected to listen on port 80, so you may allow that port to be able to be open with a unpriviledge user. You can use the following command:
      7 
      8 # sysctl net.ipv4.ip_unprivileged_port_start=80
      9 
     10 Once the images is built, run `start.sh` to create the cointainer. It will start systemd with all the service. You can test it by running:
     11 
     12 # curl exchange.taler.localhost
     13 
     14 from cli and you will get the response of the nginx running inside the container. 
     15 
     16 From now on you can kill the container, stop it and start it again. Running the `start.sh` will replace all the previous information.
     17 
     18 Starting the container won't setup the regional currency environment, for that you first have to get inside the virtual machine using `enter.sh` when the container is running.
     19 Second execute the `run.sh` script while you are inside the container. This script is based on the `main.sh` script but it will override the configuration (if you have a previous one) to make sure you can run it more than once and some other workarounds.
     20 
     21 Since the regional-currency folder will be located in the `/root` directory inside the virtual machine the run script can be run using the following command:
     22 
     23 # /root/container/run.sh
     24 
     25 After the setup is completed, the script `withdraw.sh` can help to test a withdrawal and the `diagnose.sh` to find out if there a problem.
     26 
     27 Fully Unprivileged Testing
     28 --------------------------
     29 
     30 The intention of this setup is an simple way to install, test and easy clean up. When the script start.sh is called again all the previous run is overwritten. You can then claim old containers disk using podman tools.
     31 
     32 This scripts still requires some root permissions that would also be required if you are installing and testing without podman or docker. Removing this requirement is out of scope for now.
     33 
     34 Also check systemd documentation about running systemd inside a container https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface/