[Mailman-Developers] Working towards a hassle-free Docker deployment
Hello, due to the need to modernize our Mailman installation, I want to switch two installations to Mailman3. My options currently seem to be: * Install from distro repository (Ubunut 20.04) - they only have Version 3.2.2, which does not play well with the Python version 3.8.2 that's also in the repository :-( * Install from sources - not really difficult, but I fear that regular updating might be a bit of a hassle, and integration into the system as a service needs a bit of manual work :-( * Run the Docker images created by maxking, which would probably be the most painless option for one of the sites, but there's still a caveat :-( One problem which is present in all 3 cases is that the mailman server (or container) is not on the same machine as Postfix. For mail input and output that's not a problem since Mailman speaks LMTP and SMTP, but sharing the Postfix maps between machines is a bit tricky. NFS should theoretically work, but getting all permissions right is not trivial. This is somewhat more pressing in Docker where I don't even have control over the UID running Mailman inside the container. Therefore I would like to add a socketmap service to Mailman that Postfix can query to get map information. Since this idea is probably not totally original I'd like to ask on this list whether someone already tried such a thing, and what their experiences were. Cheers, Hans-Martin ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Better documentation for Mailman Core's config options
Hey All, For the past few days, I've been trying to improve the documentation style for Mailman Core's config options. Internally, Mailman has all configurations defined in an ini formatted `schema.cfg` file, which serves as a schema for our `zope.configuration` library. We had that file simply embedded in the sphinx documentation previously as a wall of text. I ended up writing a Sphinx (our documentation generator) plugin which parses the config file and presents the same documentation with more bells and whistles so it is easier to lookup and link sections and config options.[1] The process of doing that was fun and I learnt how to write a simple sphinx plugin, so yay! It treats the comments above each config option in the ini file as it's doc and basically generates ReST text that it passes to Sphinx to parse and convert to the markup format that you see in browser. You can look at it in the source repo[2] . Do note that not all sections are documented yet, I am still figuring out what would be a good way to document template sections like `[plugins.master]` and other similar sections of that kind. [1]: https://gnu-mailman--667.org.readthedocs.build/projects/mailman/en/667/src/mailman/config/docs/config.html#configuration-options ((URL is for the PR, the main doc seems like is serving the cached version from an older build). [2]: https://gitlab.com/mailman/mailman/-/blob/master/_ext/configplugin.py -- thanks, Abhilash Raj (maxking) ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: Better documentation for Mailman Core's config options
Wow, this is amazing Abhilash! So much better than the old wall of text, and so cool that you learned how to write a Sphinx plugin while you were at it. Cheers, -Barry > On Aug 7, 2020, at 12:31, Abhilash Raj wrote: > > Hey All, > > For the past few days, I've been trying to improve the documentation > style for Mailman Core's config options. Internally, Mailman has > all configurations defined in an ini formatted `schema.cfg` file, which > serves as a schema for our `zope.configuration` library. We had that file > simply embedded in the sphinx documentation previously as a wall of text. > > I ended up writing a Sphinx (our documentation generator) plugin which > parses the config file and presents the same documentation with more > bells and whistles so it is easier to lookup and link sections and config > options.[1] > > The process of doing that was fun and I learnt how to write a simple > sphinx plugin, so yay! It treats the comments above each config option > in the ini file as it's doc and basically generates ReST text that it passes > to Sphinx to parse and convert to the markup format that you see in > browser. You can look at it in the source repo[2] . > > Do note that not all sections are documented yet, I am still figuring out what > would be a good way to document template sections like `[plugins.master]` > and other similar sections of that kind. > > [1]: > https://gnu-mailman--667.org.readthedocs.build/projects/mailman/en/667/src/mailman/config/docs/config.html#configuration-options > ((URL is for the PR, > the main doc seems like is serving the cached version from an older > build). > [2]: https://gitlab.com/mailman/mailman/-/blob/master/_ext/configplugin.py > > -- > thanks, > Abhilash Raj (maxking) > ___ > Mailman-Developers mailing list -- mailman-developers@python.org > To unsubscribe send an email to mailman-developers-le...@python.org > https://mail.python.org/mailman3/lists/mailman-developers.python.org/ > Mailman FAQ: https://wiki.list.org/x/AgA3 > > Security Policy: https://wiki.list.org/x/QIA9 signature.asc Description: Message signed with OpenPGP ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
