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 ? > 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. > 2) A network-distribution filesystem with no single point of failure. > DragonflyBSD's HAMMER filesystem can do this I think, FreeBSD has > ggatec/ggated, and Linux has some software which can do it as well. > Note that I'm not mentioning NFS because an NFS server is a single > point of failure (although many companies live with this reality and > buy something like a Network Appliance filer which is reliable). And just to run a reliable web site, you should have to endure this .. why? Someone hoping to start the next (name some popular thing) should have to endure this why? Do they not deserve reliability without mastering their operating system? What is so inherently wrong about propagating a configuration change to many nodes, without dlm, such as ocfs2 does now? Why even bother with the overhead of a cluster or network file system when one is not needed? Friendly, --Tim _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
