View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010702 | Taler | deployment and operations | public | 2025-12-02 19:56 | 2025-12-02 20:25 |
| Reporter | vecirex | Assigned To | vecirex | ||
| Priority | high | Severity | trivial | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Summary | 0010702: Test fresh install of taler-merchant v1.2.3 (in TOPF/CHF setup) [2./3.12.] | ||||
| Description | 1. - To make things predictable: As w/ a former versions, v1.2.0, there was issues in the past bc of outdated dependencies and thsu failures during install, attempt fresh containerized install; podman image in place - Do that fresh install containerized - Use another domain to make that instance available, e.g., taler.g0v.ch - for IPv4: configure reverse proxy to make TCP/443 avilable to various TLS termination end points (i.e., taler.hacktivism.ch & taler.g0v.ch) - IPv6 just needs pass through rule for TCP/443 inbound traffic and an additional automatically configured permanent IPv6 addr; given 2. By having this new instance successfully, close this ticket, then investigate initial look & feel of the admin/first merchant, creating a new ticket: to be clear, this doesn't block 0010630 and shall have lower prio (first things in taler-merchant testing first); finally, also that part of the taler-merchant must just be understandable for taler-merchant operators, but it's non-issue for the frist target group of merchants creating and using a self-provisioning instance as 0010630 aims to. | ||||
| Tags | No tags attached. | ||||
