On Sun, 26 Jul 2020 at 18:22, Mark Sapiro <mark@msapiro.net> wrote:
On 7/26/20 12:37 AM, Stephen J. Turnbull wrote:
That's not our guide, we don't support it, and at least I don't recognize the author offhand, can't speak for the rest of the team.
The author has been involved in a few threads on this list.
Now that our NO WARRANTY notice is out of the way, I will say that guide is written in very good style, with great attention to detail and appropriate warnings about delicate parts of the procedure. If you end up succeeding with it, I'll add a link to it to our docs.
It is currently linked from the first paragraph at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>.
I followed the steps outlined in the subject document and got mailman3 running. However, what is missing in that document is the process of setting up a webserver for accessing the MM3 UI. I have spent two days trying to figure out that aspect and discovered a few things (I could be wrong in what I think):
- For one to use the uwsgi.ini that is dropped in /etc/mailman3/ by the installation process, the uwsgi daemon must be installed:
*apt install uwsgi-core uwsgi*
The uwsgi.ini must be linked in the directory where the uwsgi daemon looks for config files: *cp /etc/mailman3/uwsgi.ini /etc/uwsgi/apps-available/uwsgi.ini* *ln -s /etc/uwsgi/apps-available/uwsgi.ini /etc/uwsgi/apps-enabled/uwsgi.ini*
The uwsgi daemon needs to be started *systemctl start uwsgi*
root@lists:/etc/mailman3# ps ax | grep wsgi 5838 ? S 0:00 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/uwsgi.ini --daemonize /var/log/uwsgi/app/uwsgi.log 5841 ? Sl 0:00 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/uwsgi.ini --daemonize /var/log/uwsgi/app/uwsgi.log 5842 ? Sl 0:00 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/uwsgi.ini --daemonize /var/log/uwsgi/app/uwsgi.log
Now that uwsgi daemon is running, the last step would be to configure the webserver to serve the MM3 pages.
The apache config snippet dropped by the mailman3 install process in /etc/mailman3/apache.conf contains:
<BEGIN> Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static
<Directory "/var/lib/mailman3/web/static"> Require all granted </Directory>
<IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> <END>
I added those to a virtualhost where I am running mailman2.x, but I couldn't access any of the defined aliases:
https://lists.my.site/mailman3/static/ - gives "You don't have permission to access this resource." Apache says AH01276: Cannot serve directory /var/lib/mailman3/web/static/: No matching DirectoryIndex (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm) found, and server-generated directory index forbidden by Options directive
I am stuck at that point ...
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)