some ideas with docker-compose

[daxxi13]

Hi, are you ok if :

• plex-cluster-manager and plex-cluster-proxy are created by docker-compose ?
• we change to 3 docker-compose file and one environment file (.env) ? - docker-compose-remote.yml - docker-compose-local.yml - docker-compose-plex.yml

[daxxi13]

I'll try later to run it on Kubernetes and Docker Swarm

[Fmstrat]

I might be open to this, however I sometimes find it easier to read the docker-compose file than the ENV. And I'm not sure how you would do it with one? I also don't like the idea of Plex being separated out. If that's what you like to do in your own environment, of course, however it makes it a little harder for readers to see how things are set up.

[Falconx1000]

Just my two cents, I think the proxy and plex being grouped makes the most sense. I deploy all of my services on kubernetes so I would just deploy the proxy and plex together anyway.

I think putting the manager it its own service might simplify all types of deployments, as you can just reuse the local deployment with a different name so that it is easily repeatable. This might help make troubleshooting easier as the manager is out on its own.