docker-gen VS Mailcow

Yeah, I usually do if I pass URLs to container. But again, the nginx config is completely auto-generated by docker-gen. Not sure why they don't use the container name, maybe duplicate container names? (if that's possible)

I've not got around to it, but I've always fancied creating a nice landing page that automatically updates as services come up/down, using the system jwilder created to make nginx-proxy, docker-gen. Could be a fun little project, anyway!

https://github.com/nginx-proxy/acme-companion https://github.com/nginx-proxy/docker-gen https://github.com/projectdiscovery/dnsx https://github.com/projectdiscovery/httpx https://github.com/projectdiscovery/mapcidr https://github.com/debauchee/barrier https://github.com/stedolan/jq https://github.com/ddosify/ddosify https://github.com/kubernetes-sigs/kind https://github.com/mailcow/mailcow-dockerized https://github.com/motiv-labs/janus

Then to make deployment super easy we're using nginx-proxy which uses docker-gen (and the acme-companion for automatic SSL cert generation) to automatically re-configure an nginx reverse proxy to point to your containers.

I've now got a setup using docker where the reverse proxy configuration is within the container's configuration (using nginx-proxy, which uses docker-gen). That way I just set the host, path, etc. in my container config, deploy, and the nginx servers are re-configured accordingly. No need to worry about ports and IPs then either.

I use an automated nginx reverse proxy. What this does is setup an nginx reverse proxy which uses docker-gen (follow the advice of setting it up separately). docker-gen listens for docker events such as a container being run, inspects that container for the details it needs (port, host, etc.) then configures the nginx accordingly.

I've been running mailcow [1] on a Hetzner cloud server for a few years and am pretty happy with it.

[1] https://mailcow.email

I have been searching for a self-hosted suite similar to Google Worksuite. I found the following: 1. Mailcow - https://mailcow.email/

Yes, I switched to mailcow (https://mailcow.email) and installed Roundcube via the excellent tutorial (https://docs.mailcow.email/third_party/roundcube/third_party-roundcube).

I've heard good things about mailcow

https://mailcow.email/

You can self host email if you really want to, but it's really more trouble than it's worth. If you do self host, you have to worry about the consequences of missed emails if your server or Internet ever goes down, and you'll have to use someone else's SMTP server if you don't want your emails to go directly to spam. The cheapest good SMTP server is Amazon SES, which I believe is $0.10 per 10k emails. I've been looking into mailcow for self hosting an email server and it seems the best way to go.

However, https://mailcow.email/ is the ONLY exclusion I make for that. As it's an all in one docker managed solution. Where the only things you have to worry about is the reputation of your mailing IP.

But its probably easier to use a dockerized container with all the mail stuff integrated and pre-setup like: https://mailcow.email/

If you're looking for a full solution that I haven't tried (due to resources) try: MailCow. Good luck.