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-12 17:49 |
| Reporter | vecirex | Assigned To | vecirex | ||
| Priority | high | Severity | trivial | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Target Version | 1.3 | ||||
| Summary | 0010702: Test fresh install of taler-merchant v1.2.4 a/o v1.2.5 (in TOPS/CHF setup) [2h] | ||||
| 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. | ||||
|
|
typo |
|
|
Add time estimate |
|
|
Not v1.2.3 to be freshly installed anymore, but v1.2.4 or v1.2.5: taler-merchant v1.2.4 to be released today is the candidate software to be set up for my.taler-ops.ch in production: 1. v1.2.4 will be tested in TOPS/CHF context tonight. 2. If by those tests we discover minor easy fixable issues or anything else we think is better to fix, v1.2.5 needs to be packaged and this then is the version for deployment. 3. Before that and to make sure a fresh install works without any issues (which is exactly what we need for my.taler-ops.ch), I will test either v1.2.4 or v1.2.5 on my test infra first -- depending on 2. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-12-02 19:56 | vecirex | New Issue | |
| 2025-12-02 19:56 | vecirex | Status | new => assigned |
| 2025-12-02 19:56 | vecirex | Assigned To | => vecirex |
| 2025-12-02 20:23 | vecirex | Description Updated | |
| 2025-12-02 20:25 | vecirex | Description Updated | |
| 2025-12-02 20:49 | vecirex | Relationship added | child of 0010703 |
| 2025-12-03 00:08 | vecirex | Summary | Test fresh install of taler-merchant v1.2.3 (in TOPF/CHF setup) [2./3.12.] => Test fresh install of taler-merchant v1.2.3 (in TOPS/CHF setup) [2./3.12.] |
| 2025-12-03 00:08 | vecirex | Note Added: 0026699 | |
| 2025-12-03 15:22 | vecirex | Relationship deleted | child of 0010703 |
| 2025-12-03 15:22 | vecirex | Relationship added | child of 0010630 |
| 2025-12-05 07:04 | vecirex | Summary | Test fresh install of taler-merchant v1.2.3 (in TOPS/CHF setup) [2./3.12.] => Test fresh install of taler-merchant v1.2.3 (in TOPS/CHF setup) [2h] |
| 2025-12-05 07:04 | vecirex | Note Added: 0026754 | |
| 2025-12-07 11:42 | Christian Grothoff | Target Version | => 1.3 |
| 2025-12-12 17:43 | vecirex | Summary | Test fresh install of taler-merchant v1.2.3 (in TOPS/CHF setup) [2h] => Test fresh install of taler-merchant v1.2.4 a/o v1.2.5 (in TOPS/CHF setup) [2h] |
| 2025-12-12 17:43 | vecirex | Note Added: 0026937 | |
| 2025-12-12 17:49 | vecirex | Relationship added | parent of 0010770 |
| 2025-12-12 17:49 | vecirex | Relationship replaced | related to 0010770 |
