I have been keeping my dotfiles in Git for a while now. Very handy. Since I access many systems it makes sense to keep them configured the same. Not just at a package level but also the configuration level. I've yet to do this at work but its on the to-do list. Then I just have a git pull command in the login to keep my login the system updated with my latest bash/vim or etc preferences. Putting /etc never occurred to me though.
My new web site that i am working on uses git on the backend. Document content and resources for documents, such as document-specific images are read directly from a git repository. Publishing is as easy. Just push to the repository. Whole other kind of CMS. hehe -Chris On Mon, Jul 20, 2009 at 10:55 AM, Brian Friday<[email protected]> wrote: > Hi all, > > Still working with git here and came across a interesting link this > weekend that I thought I would pass along: > > etckeeper: > Reference URL: http://kitenet.net/~joey/code/etckeeper/ > > A collection of tools to let /etc be stored in a git, mercurial, > darcs, or bzr repository. It hooks into apt (and other package > managers including yum and pacman-g2) to automatically commit changes > made to /etc during package upgrades. It tracks file metadata that > revison control systems do not normally support, but that is important > for /etc, such as the permissions of /etc/shadow. It's quite modular > and configurable, while also being simple to use if you understand the > basics of working with revision control. > > etckeeper is available in git at git://git.kitenet.net/etckeeper, or > in gitweb. It's packaged in Debian; packages for other distributions > are forthcoming. > _______________________________________________ > LinuxUsers mailing list > [email protected] > http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers >
