[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-sandcastle-ng] branch master updated: improve README
From: |
gnunet |
Subject: |
[taler-sandcastle-ng] branch master updated: improve README |
Date: |
Mon, 18 Nov 2024 22:46:05 +0100 |
This is an automated email from the git hooks/post-receive script.
dold pushed a commit to branch master
in repository sandcastle-ng.
The following commit(s) were added to refs/heads/master by this push:
new a827fd2 improve README
a827fd2 is described below
commit a827fd24afbb597d2947d0d590339bfa0e3aa3f7
Author: Florian Dold <florian@dold.me>
AuthorDate: Mon Nov 18 22:45:56 2024 +0100
improve README
---
README.md | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/README.md b/README.md
index a9a654b..4902899 100644
--- a/README.md
+++ b/README.md
@@ -9,9 +9,26 @@ has systemd running inside.
# Prerequisites
You need (on your host system):
+
* podman
* bash
+The sandcastle-ng container exposes TCP ports that serve the APIs / Web
+interfaces of the respective GNU Taler service via HTTP.
+
+Some of these services expect to be accessed via a certain hostname,
+so it is recommended that you set up the following domain names:
+
+* `exchange.$MYDOMAIN` for taler-exchange
+* `backend.$MYDOMAIN` for taler-merchant
+* `bank.$MYDOMAIN` for libeufin-bank
+* `landing.$MYDOMAIN` for the demo landing page
+* `shop.$MYDOMAIN` for the demo blog shop page
+* `donations.$MYDOMAIN` for the demo donations page
+
+Your host system should reverse-proxy HTTP(s) traffic to the respective service
+port for each of the services.
+
# Building the Container Image
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-sandcastle-ng] branch master updated: improve README,
gnunet <=