matrix-docker-ansible-deploy VS caddy-docker-proxy

Check out https://github.com/spantaleev/matrix-docker-ansible-deploy/

As some others have said, matrix is great at this.

I use this ansible playbook to set it all up: https://github.com/spantaleev/matrix-docker-ansible-deploy it supports slack and discord too.

You can also use beeper which is hosted if you don't want to self host. They employ one of the major bridge Devs so they know what they're doing.

There's also element one from the Devs of matrix but they don't support all services you're looking for.

Exactly yeah, I used this bridge with this playbook

Check the ansible instructions first: https://github.com/spantaleev/matrix-docker-ansible-deploy/tree/master

matrix-docker-ansible-deploy looks like a good way to go.

You could maybe check out this URL about setting up Oracle free tier but it could be outdated. I just recommend using the Matrix Ansible Playbook

I installed my home server via the ansible playbook, gave myself admin privileges and then enabled the api in the playbook. The playbook sets up the server with a reverse proxy and im geting an error 'NetworkError when attempting to fetch resource' when i enter in my credentials.

Yeah sorry I was on mobile when I wrote that so I didn't have it to hand.

Here it is: https://github.com/spantaleev/matrix-docker-ansible-deploy

https://github.com/lucaslorentz/caddy-docker-proxy

It handles the routing to multiple dockerized projects on one server, by scanning docker compose files for labels and automatically setting up the required caddy configuration.

My go to is always this instead:

https://github.com/lucaslorentz/caddy-docker-proxy

Single label to a docker container and with correct DNS you’ll have an automatically managed certificate right away.

I have had a great experience with using this: https://github.com/lucaslorentz/caddy-docker-proxy

It combines caddy with docker-compose labels, making it super easy to spin up new projects that can immediately be exposed.

If you want a slightly heavier but more robust solution, caddy-docker-proxy[0] is a plugin that listens to the Docker socket and automatically updates the Caddy configuration based on Docker labels you add to containers.

I.e. it makes Caddy act a bit more like Traefik. Most of the time, you'll just add the label `caddy.reverse_proxy={{upstreams http 8080}}` to your containers and the plugin will regenerate Caddy's configuration whenever the container is modified.

[0] https://github.com/lucaslorentz/caddy-docker-proxy

I disagree, Caddy works great in Docker. See https://caddyserver.com/docs/running#docker-compose, and CDP is a project that autoconfigures Caddy from labels https://github.com/lucaslorentz/caddy-docker-proxy. Regarding plugins, it's super simple to write a Dockerfile to add plugins, we ship a builder image variant that can be used to compile in any plugins you want.

````

This way, Caddy will buffer the request and give 30 seconds for your new service to get online when you're deploying a new version.

Ideally, during deployment of a new version the new version should go live and healthy before caddy starts using it (and kills the old container). I've looked at https://github.com/Wowu/docker-rollout and https://github.com/lucaslorentz/caddy-docker-proxy but haven't had time to prioritize it yet.

Docker labels support is available via a plugin https://github.com/lucaslorentz/caddy-docker-proxy

Or caddy-docker-proxy: https://github.com/lucaslorentz/caddy-docker-proxy

I am trying now for some Days to use a Caddyfile additionaly to the auto generated files from lucas lorentzes caddy repositroy. https://github.com/lucaslorentz/caddy-docker-proxy