Thank you for all comments, hints and suggestions. I'll dive a bit more in
uWSGI signals and documentations. Gunicorn seems to be a good option too,
thanks!
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web v
I found this solution pretty easy and to my likings:
$ uwsgi ... --touch-reload /var/run/any_file_actually.pid ... # launching
uwsgi
$ touch /var/run/any_file_actually.pid # anytime i want to reload all the
python code
I'm using using uWSGI in master mode with handfull of small sites and this
>
> Hello!
>
> After lot of work I'm ready to deploy my site on production. I'll use
> Nginx
> with uWSGI or fastCGI (not sure yet), and my doubt is how can I shutdown
> my
> production Django app gracefully (for make changes for example). Of course
> I can kill django-python-fcgi processes and re
On Fri, Dec 7, 2012 at 3:25 PM, Odagi wrote:
> I'll use Nginx with uWSGI or fastCGI (not sure yet), and my doubt is
> how can I shutdown my production Django app gracefully (for make
> changes for example).
on the first paragraph of the new uWSGI docs page about reloads:
"When running with the
I would actually suggest using gunicorn to run django as a stand-along app
server listening on localhost:some-local-port, and use nginx proxy passing
to redirect queries to / to the local port.
But that said, once a request is served, the listening processes are
essentially idle. So, either jus
Hello!
After lot of work I'm ready to deploy my site on production. I'll use Nginx
with uWSGI or fastCGI (not sure yet), and my doubt is how can I shutdown my
production Django app gracefully (for make changes for example). Of course
I can kill django-python-fcgi processes and restart everyth
6 matches
Mail list logo
