git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Large-scale configuration backup with GIT?

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Sep 3, 2007, 00:35 UTC
Message-ID
<46a038f90709021735n3d82061eh6d8d35989075022f@mail.gmail.com>
In-Reply-To
<7vd4x0pwjm.fsf@gitster.siamese.dyndns.org>
On 9/3/07, Junio C Hamano <gitster@pobox.com> wrote:
> This is something similar to what I and others in my group did
> long time before git was even invented.  I'd suggest you go in
> the opposite direction.

Agreed. The infrustructures.org crowd has been exploring this space quite a bit, and developing tools like isconf that allow you to manage a huge number of machines across various unixen.

And recently someone's integrated Debian APT with git tracking config files (called IsiSetup http://www.isisetup.ch/ ). I haven't reviewed it in detail, but it'd be first on my list.

> If you have 5 configurations, each of which have 20 machines
> that _should_ share that configuration (modulo obvious
> differences that come from hostname, IP address assignment,
> etc), then

Indeed. I ended up liking the makefile-stanzas approach it is incredibly simple and flexible. Add debian/rpm packages, some of the tools in the cfengine toolchain, git to track your scripts/configuration and you are golden.

For the Windows side of things, see "Real Men Don't Click" <http://isg.ee.ethz.ch/tools/realmen/> -- a bunch of unixy sysadmins with the "infrastructures.org" background took on Windows servers/desktops management -- and succeeded. PG-rated, fun for the whole family. ;-)

HTH,
martin-who-survived-the-sysadmin-wars
Previous: Junio C Hamano
Message 5 of 5 in “Large-scale configuration backup with GIT?”
  1. Jan-Benedict GlawSep 2, 2007
  2. David KastrupSep 2, 2007
  3. Jan-Benedict GlawSep 2, 2007
  4. Junio C HamanoSep 2, 2007
  5. Martin LanghoffSep 3, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.