Docker & Databases. Stack or Individual? - selfhosted - kbin.social
kbin.social
So I'm in the process of (re-) setting up my homelab and unsure about how to handle databases. Many images require a database, which the docker-compose usually provides inside the stack....

Mooching off this other post

Primary question: What do people do for their reverse proxies (and associated ACME clients)? Do you have a single unified one? Or do you use separate proxies for each stack? Or some mess in between?

My use case question: For example, I have a (mess that is a) Nextcloud instance with a separate stack with nginx and ACME, a SearXng that wants to run caddy (but has shoved into the nginx).

But now I have a Lemmy docker that has a custom(?) nginx instance, should I just port it to my existing nginx or run them side by side?

  • @NewDataEngineer
    4•1 year ago

    I’d rather not mount the docker sock into my reverse proxy,

    You don’t have to if you use the dynamic file config. I’ve mentioned this before and debated to the ends of earth for even suggesting such a thing. But it all aspects is dynamic file configuration better.

    Of you use IaC in your set up, it gets even easier because then you can just set up templates that automatically create file configs and add them to your reverse proxy seamlessly.

    Right now with one Terraform apply, I create my docker container, traefik config and my homepage service.

    • @[email protected]
      1•1 year ago

      I’ll have to look into using dynamic file configuration more heavily then. But how do you personally set up networking, if traefik doesn’t handle it all for you? Can you just tell traefik the container name from docker-compose in the dynamic file config? Also, what is IaC? Cause it sounds great.

      • @NewDataEngineer
        1•1 year ago

        IaC stands for infrastructure as code.

        Traefik’s dynamic file config just scans a folder for .yaml files. So i just generate a file automatically with the container’s network address and copy the file into traefik’s folder.

        Traefik just looks for the container address in the file (either IP or container name). The files are basically the yaml version of the docker label.