View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011388 | Taler | Web site(s) | public | 2026-05-07 18:48 | 2026-05-07 18:53 |
| Reporter | vecirex | Assigned To | vecirex | ||
| Priority | urgent | Severity | feature | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Summary | 0011388: Create stage.map.taler-ops.ch env | ||||
| Description | As discussed w/ @stefan to be useful as there are also branches to test new features in taler-ops-www.git, from where map.taler-ops.ch is built; as for the main sites, "master" branch to be used for stage.* site, changes to "stable" branch to be build source for prod. Go the same approach as for taler.net and taler-ops.ch: - CNAME: make stage.map.taler-ops.ch point to betel; TTL 600 - use same cert as for stage.taler-ops.ch, hence: renew (+add domain) - use (and slightly adapt) automation of mytops as for nginx; check before, if there are specific variables / directivies / redirects for the map.* site in place (if so, adapt mytops nginx config automation) - test firefly access using SSH www@stage.map.taler-ops.ch works - adapt taler-deployment.git to hook auto-deployment; make sure the current map.taler-ops.ch update script (using branch "master") is changed to react and to send content changes to stage.map.taler-ops.ch; create new script, adapt Makefile and invalidate.sh script to work for map.taler-ops.ch upon changes to "stable" branch - test to push changes; if it works: close ticket | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-05-07 18:48 | vecirex | New Issue | |
| 2026-05-07 18:48 | vecirex | Description Updated | |
| 2026-05-07 18:48 | vecirex | Assigned To | => vecirex |
| 2026-05-07 18:48 | vecirex | Status | new => assigned |
| 2026-05-07 18:51 | vecirex | Description Updated | |
| 2026-05-07 18:53 | vecirex | Description Updated |
