David Blevins <david.blev...@gmail.com> wrote: > In terms of clustered environments, we have a rather interesting > setup I'm really looking forward to putting to the test. We put a > lot of work into canonicalizing configuration down to this one > universal tree that is easily serializable. Think of it as an > AST -- it's not pretty to look at like source code, but the actual > configuration with the fanciness stripped away.
I like this concept. And being a former LISP hacker, I love ASTs :) > In this setup you can theoretically boot several servers with > essentially no configuration files, just give each node the > fully canonicalized configuration and they can just construct > the related runtime objects. How do you propose to give each node the config data? When working with cloud deployments, I find myself moving application config stuff away from the local filesystem to the database server, for reasons that are fairly obvious. Even if I have to hook up a WebDAV file system mount to reflect the content of the database, this is still worth the extra effort since there is only one place to update when the config data needs to be changed. -- Bjorn Danielsson Cuspy Code AB
