|
From: | Hartmut Goebel |
Subject: | Re: [Taler] sandcastle-ng: API-key for "default" merchant instance |
Date: | Sat, 16 Nov 2024 15:05:54 +0100 |
User-agent: | Mozilla Thunderbird |
I've tried to clarify overrides a bit in the README.md of sandcastle-ng.
Are you talking about a recent change? I can't spot one (just pulled master a minute ago.)
If you mean former changes: I do not understand this. I
understand that this is flexible. Anyhow, the "demo" deployment is
the default and thus scripts/demo/setup-sandcastle.sh.
So explaining how this can be customized in more details would
make live easier for newbies.
Relevant FMPOV is:
> Where are these overrides are documented? From the code I guess that
this has to go into a file "./overrides/demo". Right?
You would create an override specific to your environment, where you'd change e.g. MYDOMAIN to something else than demo.taler.net.
Well, I'm only interested in having a local environment to test
my integration with. So I'm not setting anything yet.
Maybe it's worth spending some more words on how "your
environment" is meant to be done. The sandcastle Readme also
mentions deployment.git, which AFAIU do not actually need (esp. is
says "manage the …
deployments … at https://taler.net/").
If you want to do larger changes, you could just create a modified copy of the demo setup script in scripts/$NAME/setup-sandcastle.sh and set the environment variable SANDCASTLE_SETUP_NAME=$NAME before starting the sandcastle container via ./sandcastle-run.
The Readme is a bit terse on how to actually set this variable. I
assume this is
SANDCASTLE_SETUP_NAME=$NAME ./sendcastle-run
This would not work for USE_INSECURE_SANDBOX_PASSWORDS,
or?
-- Regards Hartmut Goebel | Hartmut Goebel | h.goebel@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |
[Prev in Thread] | Current Thread | [Next in Thread] |