I'm moving my group to subversion - which I'm completely new to. It's working great though - so far. I use a post-commit hook to publish updates to the cfengine area, as well as to do some other buisness (we use a home-cooked XML host management system, and the mail XML file gets chewed on here, creating a bevvy of other files).

Best,
Erik.

Doug Chapman wrote:
The editfiles wiki page
(http://cfwiki.org/cfwiki/index.php/Editfiles_Examples) mentions using
version control on the cfengine config files.  How is everyone else
handling this?

My first idea was to use 'cvs export' to create a dated folder on the
policy server with all of the config files.
A symlink would point to the current version and could be changed
quickly for brute force rollbacks.

checkout command:
cvs export -r qa -d /var/cfengine/master-$(date +%s) cfengine/master

directory structure of /var/cfengine:
...
inputs
master-1111384286
master-1111384164
master -> master-1111384286
modules
...




--
e r i k   w i l l i a m s o n                     [EMAIL PROTECTED]
 system admin . department of computer science . university of calgary


_______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine

Reply via email to