

Can’t speak to how difficult it would be to do after the fact. My guess is just adding in the lines in the docker compose. As for CrowdSec, it seems to run in the background and I haven’t looked at it much. I’ve triggered it a few times and locked myself out. So I’ve added my home IP to the whitelist (it’s running on a VPS). It also locked out my uptime Kuma so I whitelisted that too.
I ran swarm in a homelab and ended up switching back. I don’t remember all the details I had issues with, but be aware of quorum. Here is the link to high availability docs. If one of the nodes goes down then you can’t do anything with the other. I also had issues getting everyone back online when one went down (with only two). I had three nodes, but one failed and I didn’t replace it. If one of the remaining two went offline I had to manually setup the swarm again each time. I found it to be a hassle because I didn’t have enough need for multiple nodes and high availability.
I now use Pangolin (Underlying traefik) on a VPS which VPNs back into my home where I host the sites. I have the VPN on it’s own proxmox container in the same VLAN as my servers.