On 3/20/05 10:11 PM, "Doug Chapman" <[EMAIL PROTECTED]> 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 > ... > We use subversion. All edits are done in a personal checkout, and then committed back to the subversion repository. The server (cfservd) reads its files out of a directory which is nothing more than another checkout from the subversion repository. This makes rollbacks easy since you can just cd into the cfservd directory and do a checkout of any working version you like. This is where subversion's repository-wide versioning numbers are much nicer than CVS's per-file versions since it is easy to refer to a working 'snapshot'. -Jeff _______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine
