On Sat, 2008-10-11 at 08:36 -0700, Jeremy Chadwick wrote:
> I agree completely. A centralised point for ease-of-management of the
> web server(s) themselves would be just fine, and *highly* recommended.
> I fully agree with making administrator's lives easier in that regard.
> :-)
Well, what remains is how nodes will be reached to accomplish it.
There's really only a few options:
* Use SSH or something else to push changes and reload configurations
on all effected nodes.
* Start some service with Cherokee (similar to admin) that accepts and
implements these kinds of changes
* Have Cherokee itself listen for and accept these kinds of changes
If you have a network that consists of 5 *NIX servers, and 3 Windows
servers, option #1 is not ideal.
By making it a 'part of cherokee', I meant only that nothing beyond what
comes with Cherokee should be needed to make it happen (i.e. SSH). I
would favor option #2.
However, having a single executable (cherokee) that upon some switch
went into 'config daemon mode' is interesting because it avoids writing
yet another http service to serve a relatively simple purpose.
Cheers,
--Tim
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
