hernani/koopa-admin-log
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: taler-landing how to trigger --ssh/--deploy publish

Browse source
This commit is contained in:
Hernâni Marques 2026-09-17 18:48:03 +02:00
parent 60f917fc31
commit 06ce2c58d1
No known key found for this signature in database
1 changed files with 28 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

32
scripts/taler-landing/README.md
View file

@ -147,6 +147,31 @@ podman exec taler-hacktivism-bank crontab -l # inspect
curl -sS https://bank.hacktivism.ch/intro/stats.json | python3 -m json.tool | head
```
## Publish / trigger deploy (laptop → koopa)
SoT is this git tree. Live CTR is `goa-regio-ng` on koopa (`hernani@192.168.100.95`).
There is **no** CI hook: publish is an explicit script run after commit (or after stamp).
```bash
# A) Publish current SoT HTML/nginx/js into CTR (usual after pull/edit):
./scripts/taler-landing/deploy-landings.sh --ssh
# same with explicit host / CTR:
./scripts/taler-landing/deploy-landings.sh --ssh hernani@192.168.100.95 --ctr goa-regio-ng
# B) Stamp stack-bar from live dpkg, then publish in one shot:
./scripts/taler-landing/stamp-landing-stack.sh --deploy
# C) Bump landing version footer(s), then publish:
./scripts/taler-landing/stamp-landing-version.sh --bump bank --deploy
./scripts/taler-landing/stamp-landing-version.sh --bump --all --deploy
# On koopa only (tree already synced under ~/src/koopa/koopa-admin-log):
./scripts/taler-landing/deploy-landings.sh --local
```
`--deploy` on the stamp scripts always chains into `deploy-landings.sh --ssh` (or `--local`
when already on the host), so stamp cannot leave Live behind SoT.
## Landing content version (per site)
Each landing footer shows **Bank|Exchange|Merchant landing vN** + last content
@ -155,9 +180,8 @@ change + linkified git commit. Versions are **independent** (start **v42** each)
- State: `configs/shared/landing-version.json` → `sites.bank|exchange|merchant`
- After editing one site (example bank):
```bash
./scripts/taler-landing/stamp-landing-version.sh --bump bank
git add configs/ && git commit -m "landing(bank): …"
./scripts/taler-landing/stamp-landing-version.sh bank
git add configs/ && git commit --amend --no-edit # optional pin
./scripts/taler-landing/stamp-landing-version.sh --bump bank --deploy
git add configs/ scripts/taler-landing/ && git commit # subject via git-worker
```
- Re-stamp all without bump: `./scripts/taler-landing/stamp-landing-version.sh --all`
- Re-stamp + publish: `./scripts/taler-landing/stamp-landing-version.sh --all --deploy`