On 03/01/2021 15:47, Stephen J. Turnbull wrote:
ieso@johnwillson.com writes:
Here's an interesting suggestion I received that I'm going to kick around a bit.. has anyone tried using Ansible to assist the installation process?
rivimey is very competent. That would undoubtedly be a good place to start. However, her setup may be more complicated than most folks need (IIRC, she has a multi-homed setup with Mailman core, Postorius, and HyperKitty on three separate IPs on a separate subnet in the DMZ, while Mailman was really designed for three Mailman applications running on the same host, along with the database server and MTA).
Thank you for your compliment.
I have only split mailman in two: mailman-core with the email-related parts, and postorius for the UI. As yet, although Hyperkitty "works", I haven't addressed the fact that mails get archived in folders on the email host and so (for me) hyperkitty can't see them. Ideally, they would be on the postorius/hyperkitty host, or possibly network shared
The Ansible role linked to above includes a lot of options but doesn't impose splitting the components as I've said: it merely enables it.
If anyone wants to further refine the ansible role I am happy to consider updates, especially sorting the archive!
In an earlier post on this thread (that I now see was only sent to ieso@ -- sorry!) I linked to the role I used as a starting point for my work, which does indeed do most of the "simple out-of-the-box" implementation of mailman.
the "ansible-mailman3" role by "natefoo": Mailman 3 installation, configuration, and management for Linux
There are other ansible roles which will install mysql etc as needed. If I didn't need to split the host for mailman3-core from mailman3-web, I think it would have worked out of the box.
I hadn't heard of Ansible before, but it looks perfect for this kind of situation.
I'm not sure we want to maintain an Ansible configuration, but I imagine we could stick it in contrib as "an example that works for somebody YMMV unsupported NO WARRANTY". :-)
Ansible is very good at describing deployments and I would definitely suggest investigating it if you are doing that sort of thing. One of the nice parts of Ansible is that you do not have to describe whole hosts - it will happily manage a small part without compromise. Another really nice part is that it requires very little of the host. If Ansible is not to your liking, you may find "Salt" and "Saltstack" an improvement, though for me it was not as good.
Ansible has a role archive in the form of the Ansible Galaxy website; I would suggest simply that Mailman docs mention the role's existence. As an Ansible user, that is where I would look first, so the main point of mentioning it in mailman docs is to let people who don't use Ansible know about it.
Regards,
Ruth
-- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/