Hello everyone. I created a fabfile that deploys Mezzanine sites to
Webfaction. It is not a drop-in replacement for the one provided with
Mezzanine (I'm planning on releasing one since I've moved to hosting my
sites on a VPS). Anyways, the point is that I've managed to drop
gunicorn_django
I confirm that this solved the same problem. More info here:
http://gunicorn-docs.readthedocs.org/en/latest/configure.html#configuration-file
It's been fixed two months ago:
https://github.com/stephenmcd/mezzanine/issues/870
Il giorno giovedì 16 gennaio 2014 12:35:58 UTC+1, Klamann, Norbert ha
Thanks Federico, I never stopped to realise that fix matched up with that
issue - good to know!
On Fri, Feb 28, 2014 at 10:42 AM, Federico Bruni fedel...@gmail.com wrote:
I confirm that this solved the same problem. More info here:
If the commit or the pull request message contains a reference to the issue
#number, then they will be linked each other. See:
https://help.github.com/articles/closing-issues-via-commit-messages
2014-02-28 1:03 GMT+01:00 Stephen McDonald st...@jupo.org:
Thanks Federico, I never stopped to
I repeated the whole exercise and now it works .
gunicorn.conf.py is changed an looks like that.
mezzanine@wsa02:~/mezz_test/project$ cat gunicorn.conf.py
from __future__ import unicode_literals
import multiprocessing
bind = 127.0.0.1:8000
workers = multiprocessing.cpu_count() * 2 + 1
loglevel
At least for the most basic deployment of mezzanine (ie. no custom theme
app yet) I seem to have resolved the issue.
Although I did a few different things, I think that the major factor was
changing the gunicorn port from 8000 to anything else (8001, ).
I'll keep you posted as to whether
That gives me:
!!!
!!! WARNING: This command is deprecated.
!!!
!!! You should now run your application with the WSGI interface
!!! installed with your project. Ex.:
!!!
!!! gunicorn myproject.wsgi:application
!!!
!!! See
