a downtime of the server where I host my TG app has remeinded me to look into
controlling starting/stopping the CherryPy process with some form of boot scripts.
A little googeling brought up several options (for a Linux system), among these
- write a SysV init script (cumbersome & no automatic restarting :-()
- daemontools
- supervisord
How do other people do this? How do daemontools and supervisord compare? Both
seem really straightforward to set up and I'm wondering which are the pros &
cons for each.
Chris
I'm feeling a bit odd, talking only to myself here ;-) but since nobody had to
share any experiences on this, I had a look at supervisor myself today and
wrote up a little blog post on my experience in setting it up to control a
TurboGears application. You can read it here:
http://paddyland.serveblog.net/article/12
Short summary: works well, but rather laborious to set up.
Chris
I have a similar writeup here:
It doesn't cover setting up supervisord as much, but it also gets into
using workingenv.py to isolate app environments.
--
anders pearson : http://www.columbia.edu/~anders/
C C N M T L : http://www.ccnmtl.columbia.edu/
weblog : http://thraxil.org/
Yes, I had read that and trying out workingenv.py is on my TODO list as
well. BTW, it is only through a comment on your post, that I learned
about supervisor2, which was after I already had set up version 1.0.7.
In the meantime, I installed supervisor2 as well but I haven't been
sucessfull in starting my TG app through it so far. I will report back
on this later.
Chris