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/
-- thanks, Abhilash Raj