From db7815dc8792bd0d5b75d7d63ff3826c8bd06b44 Mon Sep 17 00:00:00 2001 From: Florian Dold Date: Tue, 17 Oct 2023 13:22:53 +0200 Subject: WIP --- sandcastle-ng/README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/sandcastle-ng/README.md b/sandcastle-ng/README.md index 0f17ade..34328c4 100644 --- a/sandcastle-ng/README.md +++ b/sandcastle-ng/README.md @@ -40,6 +40,12 @@ The main adjustments to be made are: Run ``./sandcastle-run`` to run the single container. The container will be named taler-sandcastle. +You can run the container in the background by passing ``-d``. Note that ``./sandcastle-run`` is just +a wrapper around ``podman run``. + +The running container published ports to the host as defined in ``./sandcastle-run``. +You can manually verify these port mappings via ``podman port taler-sandcastle``. + # Stopping the deployment ``` @@ -56,6 +62,7 @@ podman exec -it taler-sandcastle /bin/bash ``` Or, as a shortcut: + ``` ./sandcastle-enter ``` @@ -113,6 +120,8 @@ You can always manually run the script inside the container as ``/scripts/setup- Taler deployment on the podman host. * Instead of exposing HTTP ports, we could expose everything via unix domain sockets, avoiding port collision problems. +* Instead of requiring the reverse proxy to handle TLS, + the sandcastle container itself could do TLS termination with caddy. * To improve performance, allow connecting to an external database * Make it easy to import and export the persistent data * Extra tooling to checkpoint images/containers to revert to a previous -- cgit v1.2.3