This is why it's important to keep server configurations in a configuration management system, like Chef, Puppet, cfengine, Ansible, Salt Stack, etc. When set up right, the configuration management will put back any unwanted OS changes, or at the very least tell after an upgrade what files no longer contain your edits.
On Tue, Nov 04, 2014 at 11:59:02AM -0500, nxnw wrote: ... > 1. Mostly good news - after the OS and server.app upgrades, mailman was > (mostly) running. The only thing that was not working was the web interface. > After a bit of investigation, I found that the upgrade overwrote > /Library/Server/Web/Config/apache2/httpd_server_app.conf, so that file had to > be edited (again) to add the following: > > #Mailman > Include /private/etc/apache2/extra/httpd-mailman.conf > > I put the above right after "Include > /Library/Server/Web/Config/apache2/other/*.conf". Apache must be restarted > after the edit. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
