The entire process I followed is below:

•     sudo apt-get update

•     sudo apt-get install git python3-dev python3-pip python-dev

  python-pip python-virtualenv

•     sudo apt-get install nodejs npm

•     sudo npm install -g less

  You don't need {less,nodejs,npm} Hyperkitty switched from less to sass

•     sudo ln -s /usr/bin/nodejs /usr/bin/node

•     created new user 'mailmanuser'

•     'mkdir /opt/mailman'

•     'sudo chown mailmanuser:mailmanuser mailman'

•     'su mailman'

  This is inconsistent with your other instructions. I guess it's just a typo

•     'cd /opt/mailman'

•     git clone https://gitlab.com/mailman/mailman-bundler.git

•     virtualenv -p /usr/lib/python2.7 venv

•     source venv/bin/activate

•     changed password in mailman_web/testing.py

•     cd mailman-bundler

•     pip install zc.buildout

•     buildout

•     sudo apt-get install ruby-sass

•     ./bin/mailman-post-update

•     ./bin/mailman-web-django-admin createsuperuser

•     ./bin/mailman start

•     ./bin/mailman-web-django-admin runserver 0.0.0.0:8000

I have attached the django and mailman logs and the top of the page I get back from the server

I must have missed something but I don't really know where to go from here... Please can you review and advise if there is anything that I have missed? You didn't miss anything. The mistake was on our side. mailman-bundler used to install mailman==3.0.2 which didn't limit the falcon version but is incompatible with the latest. mailman==3.0.3 was released to fix this issue but mailman-bundler wasn't updated until today.

You can either start fresh or activate the python3.4 virtualenv and run pip install --upgrade falcon==0.3.0 After that restart mailman and everything should be fine.

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

On 04/19/2016 11:40 AM, Andrew Hodgson wrote:

I have often wondered if there was a howto on how this specific mailman3.org server was built, so it gives us a production-like template to follow?

Sort of, but it's not (yet) public. The process I followed is very convoluted and not what I would recommend anyone follow. Part of the issue is I started with mailman-bundler not using a venv, but bundler still installs a lot of stuff in Python 2 and Python 3 venvs. I then proceeded to install the git master branches of mailman, mailmanclient, mailman-hyperkitty, hyperkitty and postorius and their dependencies system wide and ripped out most of the venv stuff.

Then there were issues because I'm running django 1.9 only and that's not compatible with django_haystack 2.4.1, so I upgraded that to 2.5.dev0 from GitHub, but that now has a compatibility issue with HyperKitty which I have worked around.

As you can see this is not a clean process. If I were starting over with what I've learned, I'd probably let bundler install it all in venvs and then upgrade the venvs to the git master branches.

There would still be issues, but it would be cleaner.

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On Apr 20, 2016, at 08:11 AM, Andrew Hodgson wrote:

My main thing when looking at this is how package managers are likely to package Mailman3, especially from a Debian point of view. I know I can't second guess what is going to be done, but would like to try to build using similar goals if possible.

There have been ongoing discussions on mailman-developers and the relevant Debian mailing lists about packaging Mailman 3.

Pierre-Elliott Bécue has been leading the effort, e.g.

https://mail.python.org/pipermail/mailman-developers/2016-February/025395.ht...

Cheers, -Barry