View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009412 | Taler | sandcastle (containerized demo deployment) | public | 2024-12-20 18:03 | 2026-08-22 19:36 |
| Reporter | sebasjm | Assigned To | Florian Dold | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Target Version | post-1.0 | ||||
| Summary | 0009412: add a status.html which list all the components with status + version | ||||
| Description | so we can go to http://<env>.taler.net/status.html and see if everything is working and maybe a /status.json to check from CLI | ||||
| Tags | No tags attached. | ||||
|
|
Implemented, but only static information. I don't think we want a separate component just for implementing dynamic status requests. https://test.taler.net/metrics/sandcastle-status |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-12-20 18:03 | sebasjm | New Issue | |
| 2024-12-20 18:03 | sebasjm | Status | new => assigned |
| 2024-12-20 18:03 | sebasjm | Assigned To | => sebasjm |
| 2024-12-27 22:55 | Christian Grothoff | Target Version | 1.0 => 1.0 stretch goals |
| 2025-04-17 22:23 | Christian Grothoff | Target Version | 1.0 stretch goals => post-1.0 |
| 2025-04-18 00:31 | Christian Grothoff | Assigned To | sebasjm => |
| 2025-04-18 00:31 | Christian Grothoff | Status | assigned => confirmed |
| 2026-08-22 19:36 | Florian Dold | Assigned To | => Florian Dold |
| 2026-08-22 19:36 | Florian Dold | Status | confirmed => resolved |
| 2026-08-22 19:36 | Florian Dold | Resolution | open => fixed |
| 2026-08-22 19:36 | Florian Dold | Note Added: 0029552 |
