Maybe something to think about for the long term, as I don't think this will be easy to implement:
It would be nice if Tuliprox could be made highly available via Docker by running multiple Tuliprox instances using the same configuration. This way you could for example "drain" an Tuliprox Docker instance (via a proxy like nginx, Traefik, Caddy, etc.), so maintenance (like new Tuliprox updates) could be performed on instances which are drained (and have no active client connections).
Currently it's not possible to start multiple Docker instances which share the same configuration, because (e.g.):
- The Tuliprox instances would need to know about each others active provider connections, so provider connections won't get reused by the other Tuliprox instance. Maybe a shared database can be used for this to keep track of active provider connections.
- Scheduled playlist updates will be performed by multiple instances at the same time, because they're using the same configuration.
- ...