Files
Ping/backend
Admin f043ef3b85 Point at the shared Infrastructure repo instead of Musify's folder
Ping already reused Musify's Zitadel and SeaweedFS, but did so through a
hardcoded relative path into Musify's own deploy folder
(../../../Musify/MusifyM/deploy/zitadel/.output), which only worked
because Musify happened to be the one running them. Those services now
live in a separate Infrastructure repository instead, so this points
there.

Also drops Ping's own Postgres container in favor of Infrastructure's
shared instance (its own ping_db database), with a wait-for-postgres
one-shot replacing the in-file health check.
2026-09-21 22:09:22 +02:00
..
2026-09-21 19:32:55 +02:00
2026-09-21 19:32:55 +02:00
2026-09-21 19:32:55 +02:00
2026-09-21 19:32:55 +02:00
2026-09-21 19:32:55 +02:00
2026-09-21 19:32:55 +02:00
2026-09-21 19:32:55 +02:00
2026-09-21 19:32:55 +02:00
2026-09-21 19:32:55 +02:00
2026-09-21 19:32:55 +02:00