>chausette allows you to run over a unix socket, and this allows
circusd to easily spin up a new backend (with different code) and
transfer requests to that unix socket, whilst leaving the old backend
still running.

This was the killer feature that I started using uwsgi, you can reload your
new django code without uwsgi closing the socket, in the worst case some
requests may feel a little delay but won't feel any downtime

I once even did a crazy thing: a form that updated and reload its own
django code (git pull and uwsgi reload), it worked great, user would click
on the button to update the system, the request would come and the user
would get the updated version on reload (because form response is redirect)

my only problem was doing the same trick on cygwin, but that's another story

On Fri, May 15, 2015 at 11:33 AM, Tom Evans <tevans...@googlemail.com>
wrote:

> On Thu, May 14, 2015 at 4:18 PM, Marc Aymerich <glicer...@gmail.com>
> wrote:
> > On Thu, May 14, 2015 at 11:26 AM, Tom Evans <tevans...@googlemail.com>
> wrote:
> >> On our app servers we typically use Apache with worker MPM and
> >> mod_wsgi, although we have a few nginx+uwsgi sites, and I would dearly
> >> love some time to play around with a circusd + chausette + celery
> >> setup.
> >
> >
> > Hi Tom,
> > never heard about circusd and chaussette, but it sounds interesting.
> >
> > I believe the advantage of this setup pays when you have several
> > independent low-traffic applications, because you don't want all of
> > them to have preforked wsgi worker processes, not even the master
> > process. I think uwsgi can do that (emperor mode, cheaper subsystem),
> > but circusd will allow you to do the same which celery (celery needs
> > at least one master per pool). Is this the main point? I'm asking
> > because I can only find just a couple of blogposts and the
> > documentation is concise, neither mention the real tangible advantage
> > over traditional deployments.
> >
>
> There are few very cool things I like about circusd + chaussette,
> chausette allows you to run over a unix socket, and this allows
> circusd to easily spin up a new backend (with different code) and
> transfer requests to that unix socket, whilst leaving the old backend
> still running.
>
> This means zero downtime when doing a code upgrade, and instant
> failback to the old application if for some reason you don't like what
> was pushed.
>
> The second thing is that circusd is a process manager like
> supervisord, but it allows for dynamic operation - you can run celery
> worker processes underneath it, and spin up/spin down worker processes
> as you see fit to allow for load.
>
> The third is that circusd is accessed by a web interface, which allows
> for simple day to day use and also simplifies how admins and sysadmins
> can interact with it. Its very easy for our sysadmins to control
> things they can just fire http requests at.
>
> Cheers
>
> Tom
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAFHbX1Kekp9cNqqcZPjxfpWgGS%2BxGhuaaE9VT35Hd79S%3Dv8kbg%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFWa6tKVfSGznv5NNzBfqPkakCn_oofaDe28Nf6Nmb6mXP2zoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to