I found this comment on my original thread helpful: accolon
Basically it says let the acme-mailcow service manage ACME for everything mailcow related, and my non-mailcow ACME/certbot for everything else. I just need to point my reverse proxy to the nginx-mailcow service, and point to the mailcow certs.
I was hoping someone would respond to this topic, but I’m afraid it hasn’t gotten any visibility. I read through the mailcow docker-compose.yaml file, and it makes sense that I really shouldn’t touch this file at all. I found some interesting things in that file, especially setting up the Docker network bridge. I did try to emulate some of that in my non-mailcow stack, but it didn’t quite work like I expected.
That’s likely due to my non-mailcow docker-compose.yml being on version 3.8, while the mailcow version is on 2.1. I’m not looking for help from the mailcow community on that, I have the Docker community for that (irc://#docker@libera).
In any case I am several weeks away from running
docker compose up -d in my first mailcow stack. I’m about to launch a new website for a community organization I run from my existing VPS, and will be adding 200 users next week. I need to see what kind of load that puts on the VPS. I have no idea how many concurrent users I’ll have, probably not close to the maximum number of members, but I have no way to gauge the actual load before launch.
I’ll make the decision on whether it can support mailcow under such a load. The initial mailcow stack will only have one user (me), so I’m pretty sure this VPS will be able to handle it.