Not a holy war - just some salient facts

Robert Figura nc-figuraro at netcologne.de
Sun Apr 11 08:37:07 CDT 2010


Mike Meyer <mwm at mired.org> wrote:
> For this one use case - tracking config
> files in situ - that the perforce server tracks what is checked out on
> the client is a major win. Everything I need to know to recreate any
> client from scratch is available on the server, without having to back
> up the client systems. That's not true with any VCS that keeps the
> data about what's checked out in the workspace - which I believe is
> pretty much every VCS *but* perforce.

That is easy enough to do outside mercurial. This is what we use here:

Have a branch per setup with its config files.
Have a dist server hosting a repo per branch which is protected by
htpasswd per install.
Pushing #branch to ssh://dist.../repo/branch using a list is a trivial
script
Editing htpasswd files may be accessible even to administration
personnel via various web config software.
Setting up a new install is basically cloning using the right
credentials.
Finally creating a new branch can also be fully automated, we use
a shell script with some sed to do the cgi config here.

I think that qualifies since it is quickly understood by any unix admin
without deeper perforce knowledge.

Kind Regards
  - Robert Figura

-- 
http://digital-gecko.net/




More information about the Mercurial mailing list