Hi Abhilash & everybody,
thanks for your help! We got the configuration working now, see below - proxy modules have to be loaded here to make it work.
Regards, Alex
<VirtualHost *:443> ServerAdmin webmaster@localhost ServerName mailman.example.org Alias /static /opt/mailman/web/static Alias /favicon.ico /opt/mailman/web/static/hyperkitty/img/favicon.ico ProxyPassMatch ^/static/* ! ProxyPass / http://172.19.199.3:8000/ ProxyPassReverse / http://172.19.199.3:8000/ <Directory /> Allow from all Require all granted </Directory> <Directory /opt/mailman/web/static/hyperkitty/img/> Allow from all Require all granted </Directory> ErrorLog ${APACHE_LOG_DIR}/error.log LogLevel warn CustomLog ${APACHE_LOG_DIR}/access.log combined # ssl config here ... </VirtualHost>
Am 28.06.17 um 15:11 schrieb Abhilash Raj:
Hi Alex,
On 28 June 2017 at 02:28, Alexander Klotz <alexk@kulturserver.de> wrote:
Hi Abhilash,
thanks for the info regarding the docker, we could fix this issue now.
As for the webserver, we use apache instead of nginx - our current configuration looks like this and won't work - how should we change it?
Alias /static /opt/mailman/web/static ProxyPass / http://172.19.199.3:8000/ ProxyPassReverse / http://172.19.199.3:8000/Here are a few resources that might help you setting up Apache with uwsgi
https://uwsgi-docs.readthedocs.io/en/latest/Apache.html http://voorloopnul.com/blog/setting-up-django-with-apache-and-uwsgi-ubuntu-1... https://uwsgi-docs.readthedocs.io/en/latest/WebServers.html
Please share the complete configuration here if you get it working, I can add it to documentation so that others can use it too :)
Thanks again, Alex
Am 27.06.17 um 18:39 schrieb Abhilash Raj:
Hi Alex,
On 27 June 2017 at 05:05, Alexander Klotz <alexk@kulturserver.de> wrote:
Hi everyone,
we are experiencing some issues trying to run mailman3 on our server.
First, when starting docker-compose up -d the mailman-web container is not started. The log shows:
mailman-web | useradd: user 'mailman' already exists
This is an old issue, should be resolved now. If you use the new images with tag "0.1" or "0.1.1", that should not be a problem.
The new docker-compose files have changed to reflect that. You might have to remove the old containers to use the new image:
$ docker-compose stop $ docker-compose rm $ docker pull maxking/mailman-core:0.1 $ docker pull maxking/mailman-web:0.1 # Make sure docker-compose.yaml file uses these images instead of "latest" ones. $ docker-compose up -d
If we start the container with docker-compose up (without -d), all containers start accurately. Are there other files integrated / processed when starting docker-compose up with -d?
Secondly, no css and javascript-elements, as well as images are embedded in the web surface. In the mailman-web log we can see they aren't found (Error 404), but trying with docker-compose exec -T mailman-web ls /opt/mailman-.../static/.../... they actually can be found.
Uwsgi server running the Django inside the containers doesn't serve static files. You have to serve them directly with your web server. Configuration for Nginx looks something like this1
Can anybody tell me why these problems appear and how to solve them? Any
help would be highly appreciated.
Thanks & Regards, Alex Klotz
(culturebase editorial staff)
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/