Avoid PyInfra #7
Description
PyInfra is not a standard way to deploy stuff AFAIK. There's plenty more standardised ways to install complex servers with dependencies such as Docker or Podman. Find the pros and cons of changing it.
After checking the Docker branch and seeing some very big errors on how to use containers I see there's no other option than to get rid of PyInfra altogether.
The target system should be definitely Docker and the target OS needs to be carefully thought due to the custom-made Dovecot version. See here: dovecot/core#216 I'd like to give a try to compiling it so that I can use the latest and greatest version with the patches applied on that PR instead of a froze-in-time version. (Also this would allow to use Debian 13, since this is where my first attempt broke and forced me to use Debian 12).
In case you want to give a try to Dovecot from NIxos: https://wiki.nixos.org/wiki/Dovecot
Beware there seems to be many changes in config file format from Dovecot 2.3 to 2.4
This seems to be the beginning of everything:
And from there each one of those services should be taken out of PyInfra one by one, at the beginning on a Debian instance outside Docker. Once it runs with none of them deployed using PyInfra them it can easily be Dockerised.
I do wonder why Unbound is needed, I'm not configuring DNSSEC