mash-playbook VS uptime-kuma-api

Sometimes the easiest and quickest way to try (or even deploy) a new service is by using the recommended docker-compose-setup that they often have as an example. But if you have an existing infrastructure, like we do with the great mother of all self-hosting ansible playbooks, this isn't always easy to integrate. In particular when that infrastructure is managed and started and stopped independently from the additional docker-compose you intend to add. Lucky, who is running their out-most proxy using traefik, because with just a few extra labels your docker-compose becomes available TLS-certs included.

Yes! And don't forget MASH [0], its a collection of Ansible roles that is compatible with the Matrix Docker Ansible Deploy playbook. In case you want to add more services to your Matrix server.

[0]: https://github.com/mother-of-all-self-hosting/mash-playbook

This is why I like https://github.com/mother-of-all-self-hosting/mash-playbook and its associated Ansible roles for configuring various services.

All the portability of Docker, plus (something close to) the ease of use of installing a distro package like an .rpm or .deb.

I use Authentik. Is speaks LADP, OICD, OAUTH and SAML so most use cases are already included. For everything else there is the option of using a proxy provider with an appropriate webserver that uses [Forward aut](https://doc.traefik.io/traefik/middlewares/http/forwardauth/). I never used Forward Auth but the general setup is discussed here: https://github.com/mother-of-all-self-hosting/mash-playbook/issues/50

more here

I found someone's effort on github https://github.com/lucasheld/uptime-kuma-api Haven't seen anyone write about it through.