View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011791 | Taler | deployment and operations | public | 2026-09-11 19:12 | 2026-09-18 14:05 |
| Reporter | Florian Dold | Assigned To | vecirex | ||
| Priority | high | Severity | feature | Reproducibility | N/A |
| Status | confirmed | Resolution | open | ||
| Target Version | 1.7 | ||||
| Summary | 0011791: migrate mytops setup to ansible [wip: tests in betel first] | ||||
| Description | We already have lots of examples of how the merchant is set up via ansible, the mytops-admin-log should also be ansible-based. | ||||
| Tags | mytops, quality, reproducability, srv-betel | ||||
|
|
Yes, there's mytops-local as a first approach for loopback config, tested to work in a container; mytops-vanilla underway without STAGE_ENV, to lead then to two branches master for stage and prod for mytops prod, as with taler.net and taler-ops.ch. New branch master then to try in a container on real betel, if it works, recreate betel. |
|
|
After FP work. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-09-11 19:12 | Florian Dold | New Issue | |
| 2026-09-11 19:12 | Florian Dold | Status | new => assigned |
| 2026-09-11 19:12 | Florian Dold | Assigned To | => vecirex |
| 2026-09-15 18:26 | vecirex | Note Added: 0029975 | |
| 2026-09-15 18:26 | vecirex | Tag Attached: mytops | |
| 2026-09-15 18:26 | vecirex | Tag Attached: srv-betel | |
| 2026-09-15 18:26 | vecirex | Tag Attached: reproducability | |
| 2026-09-15 18:28 | vecirex | Note Edited: 0029975 | |
| 2026-09-16 03:55 | vecirex | Summary | migrate mytops setup to ansible => migrate mytops setup to ansible [wip: tests in betel first] |
| 2026-09-18 12:52 | vecirex | Status | assigned => confirmed |
| 2026-09-18 13:29 | vecirex | Note Added: 0030004 | |
| 2026-09-18 14:05 | vecirex | Tag Attached: quality |
