Have a Premade Docker Compose File of full Setup

[Ryu945]

Description:

Can you have an example docker compose file of everything setup. This includes reverse proxy, letsencrypt, redis, synapse, coturn and jitsi . It would make deploying an instance a lot easier. The details of a docker compose file answer a lot of questions of how things are setup and how they work.

[maxkratz]

IMO an example docker-compose.yml file would only cover one way to configure the services. For example, my instance does not use Redis and a self-hosted Jitsi instance at all. So what is an "everything setup"?

Maybe it would be better to provide a set of docker-compose stacks to keep it more modular:

• Reverse proxy, LetsEncrypt (could probably be found in the documentation of the reverse proxy of your choice)
• Synapse, Postgres database
• Coturn
• Jitsi (could be found in the Jitsi documentation/Github resources)

[Ryu945]

Maybe it would be better to provide a set of docker-compose stacks to keep it more modular:

That would be useful to clear up confusion. I know that Docker Compose is pretty modular as it is so you can look at an everything file and derive what is needed. This would make things more clear to do it that way.

Right now, I have been trying to setup a server for months but everything is so unclear that I haven't had any success yet in figuring all this out. Chat support doesn't explain every detail you need to know to setup a server. Even if you found someone willing to take the time to do this, chat simply doesn't know enough about Matrix to answer the questions. If you don't do anything other then an ansible setup or a basic Matrix server with nothing else then no one seems to know anything about the setup at all.

[jawjawjaw]

I also struggle with server setup-mostly problems with local development setup of two matrix severs running on separate docker networks and more detailed docker-compose example would definitely help a lot.
I found it quite hard to setup two working instances of dockerized synapse on one machine, I have 2 functioning synapse servers with separate postgres instances, but they're not able to talk to each other - probably due to some Docker network DNS issues(but those containers can ping themselves, so I am not sure why DNS issue is raised by synapse..)
I am aiming to have similar setup as described in this comment. Sounds easy but there's always some catch.