On Tue, Oct 20, 2015 at 12:29 PM, Chris Withers
> What does pserve use?
pserve is a generic runner. It uses whatever server is pointed to in the
[server:main] section by default. This is taken care of by PasteDeploy as
part of loading the ini file.
What does pserve use?
What do people use for their development process? (I guess the
equivalent of django's manage.py runserver).
Sorry, I feel like I'm missing some docs somewhere, so please feel free
to point me their way...
On 29/09/2015 14:35, Bastian Kuberek wrote:
For development I use nginx on http/https default ports, serving static
directly and proxypass back to pserve for dynamic content.
The staging/production environment just swaps out the proxypass for uwsgi.
Everything in nginx is built out with components/includes, so it's
I use nginx+waitress in production. Except once in a blue moon I've used
gunicorn for something with long persistent connections. (Streaming music
server, anything that uses socket.io, etc...)
On Tue, Sep 29, 2015 at 9:35 AM, Bastian Kuberek wrote:
> Like others, I