Re: history

On Tue, Sep 16, 2003 at 10:44:33PM +0100, Jonathan Hogg wrote:
> 
> I think it's fairly common with ARK deployments to put the XML configuration
> files under revision control. Given sensible commit comments, you can record
> a history of configuration changes and their reason. Then you can diff each
> file against a previous revision to later examine the changes.
> 
> Assuming your config files completely and accurately describe your site
> (minus data) at each particular moment, then having them under revision
> control should allow you to recreate your site as it was at any past moment,
> and allow you to examine the configuration changes that exist between then
> and now.
> 
> Of course it's never that simple as inevitably some cruft leaks in ;-)
> 
> I'm not sure if you mean something more specific that this.

I was actually looking for history at an object level. Unless one is
fairly rigourous about keeping a single object per xml/other source
file, it's hard to see what changes have been made to just _this_ object
in the past.

It ties in with my history comments in my previous mail to will; one may
want to know/store the history of a machine (which is really just another
object). CVS/other can be used, but to me it seems like that's below the
level one thinks of the (host/package) object at - you may want to not
version this stuff (for one reason or another), or your filestore (where
you keep ark source) may not be versioned, etc.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf