selfhosted VS envconsul

Here’s a guide a wrote a while back after I typed this up a bunch of times in comments https://github.com/subdavis/selfhosted/blob/main/docs/lan-only-routes.md

https://github.com/BaptisteBdn/docker-selfhosted-apps https://github.com/subdavis/selfhosted https://github.com/htpcBeginner/docker-traefik https://github.com/petersem/dockerholics

Link to my full configuration.

Here’s a link to my full config, which is really close to what you’re trying to do. https://github.com/subdavis/selfhosted

I do this exact thing, see my config here https://github.com/subdavis/selfhosted

I would tend to opt for multiple database instances, but you can still use one large docker-compose.yml file if you want. My example is here: https://github.com/subdavis/selfhosted/blob/main/docker-compose.yml

Might not perfectly fit but I think that was one of the ideas behind - https://github.com/hashicorp/envconsul (which can use Vault as a source), and probably to a degree consul-template (though a quick skim of the documentation and I'm not sure if can use Vault as a source.)

You have envchain to store secrets as ENV variables in your keyring and execute commands:

https://github.com/sorah/envchain

Not really something you would use for production web apps, I think envconsul covers that usecase:

https://github.com/hashicorp/envconsul

Have you looked into Hashicorp's consul + envconsul? You can also encrypt data using their vault.