On 11-oct-08, at 14:49, Jeremy Chadwick wrote: > On Sat, Oct 11, 2008 at 08:38:52PM +0800, Tim Post wrote: >> On Sat, 2008-10-11 at 04:31 -0700, Jeremy Chadwick wrote: >>> Is solving this problem *really* the job of a web server? The >>> answer to >>> this question should be: no it is not. >> >> Is that so? >> >>> The web server should handle web server "things". >> >> Updating a single text configuration file from a central point is >> not a >> 'thing' for web servers to do ? > > No. Web servers serve content; web servers do not distribute files to > other machines.
You guys are both right. Web Server should not distribute content among cluster nodes. I think we all agree on that. However, expanding cherokee-admin -or even developing a new tool- to support multi-node set ups sounds quite interesting. Obviously, the web servers should not to do it, but another higher level tool. >>> What you're >>> describing is the need for either: >>> >>> 1) A series of administrative scripts that can distribute >>> configuration >>> files to numerous servers when changes are made. This is how a >>> lot of >>> companies do it. Have you looked at cfengine? Please do. >> >> And years ago we made fire with sticks. Yes, I have looked at it. > > Administrative scripts are not something from the 70s. They are a key > piece of problem-solving and administrative task completion on UNIX. > If you are a system administrator who does not know shell scripting or > how to use utilities like scp or rsync, you likely shouldn't be the > sole > administrator of a system (you should be a junior SA and have someone > senior above you who can "show you the ropes"). Again, both points are view are right IMO. An administration script is fair enough. It does its job, and usually solves the problem. But again, adding a central panel from which admins could manage a whole web server cluster would be really convenient, don't you think? >>> > A web server's job is to serve content over HTTP, not to do things > like > distribute configuration file changes to machines over a network. > Distributing files to multitudes of machine is not the job for a web > server. As I see it, it's more like putting tools in place to make Cherokee clusters administration easier. The content distribution is a complete different matter. -- Greetings, alo http://www.alobbs.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
