On 05/05/2016 04:15 AM, Mark Sapiro wrote:
On 05/04/2016 09:45 AM, Andrew Hodgson wrote:
Anyway, I have compiled Mailman3, and the web interface is coming up. Bringing up the list of lists initially gave me an exception, and I saw a 5xx error in the mailman.log file in /opt/mailman/var/logs. I read up on this and as a result downgraded Falcon<1.0 in the Python 3.4 venv.
I am still unable to browse the list of lists with a 500 error, only this time I am not getting an entry in the mailman.log indicating there is an issue, and I am wondering if there are more detailed logs that can be switched on?
There are the web server logs and there is the mailman-web configured in LOGGING:handlers:file in (using bundler) mailman-bundler/mailman-web/production.py (or testing.py). The production default is /var/log/mailman-web/mailman-web.log; the testing default is /opt/mailman/var/mailman-web/hyperkitty.log.
You might also get a 500 error because of a django error. If you have debugging enabled, you should see the trace in the browser. If not, then you should get an email (If you configured am admin email) Otherwise the files above should contain information about it.
The other question I have is on Sassc. I believe the default Mailman web interface has now switched to the Ruby implementation of Sass, but is this correct? The documentation on the Mailman-Bundler site seems to suggest that Sassc is still the default.
I think the bundler doc is out of date on this.
Hyperkitty switched from less to sass. Which sass compiler you use is irrelevant. You can use the ruby implementation (but it pulls in ruby as a dep). I am using the C preprocessor from libsass.org I will go over the docs and see if that section is unclear.