Re: history

[Jonathan H. <jon...@on...>]

[Oops! Sent this offlist by mistake.]

On 16/9/03 0:58, Rudolph Pereira wrote:

> By history, I mean (at least) something like a changelog for an object,
> that's actually kept with the object (or linked to it), rather than
> implicitly in (say) the CVS changelog in the repository for the xml
> files. Even better would be some kind of versioned view of an object
> - e.g having (in the ark/xml description) something like "this was
> version x.xx of foo, this is y.yy" and possibly some support for
> generating a "diff" of sorts.
> 
> Hopefully I've not been too vague and someone understands what I'm
> talking about, and even better, knows how to do it. Note that I'm
> looking at rather than using ark/arusha at the moment, so feel free to
> point me in the right direction if I've missed something.

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.

Jonathan