Erin Justice writes:
The addition to the virtual hosts file is:
<VirtualHost *:80> #Mailman3 stuff ServerName mailman.local
Alias /static /Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/static <Directory "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/static"> Order deny,allow Allow from all </Directory>
WSGIScriptAlias / /Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project/wsgi.py
<Directory "/Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/mailman-suite_project"> <Files wsgi.py> Order deny,allow Allow from all </Files> </Directory> </VirtualHost>
All of the above looks OK to me.
I also have the following in my https.conf.
WSGIPythonPath /Applications/MAMP/Library/lib/python2.7/
I think this is unnecessary as long as python is getting run: it knows where to find itself. On the other hand, you need to tell WSGI where the Django project (mailman-suite_project?) lives. I use a different syntax:
WSGIDaemonProcess site python-path=/home/django/project user=django group=django display-name=django
where ~django/project is the Django project root, containing manage.py and site/, where site/ contains settings.py, wsgi.py, and all that stuff. So my guess is you need
WSGIPythonPath /Applications/MAMP/Library/lib/python2.7/site-packages/mailman-suite/
I'm not sure why that ended up in httpd.conf. WSGIDaemonProcess works fine for me in the VirtualHost stanza that configures Mailman.
Steve