Manage the files you care about with puppet, keeping the modules in a git repo. If you are concerned about files changing that aren't managed with puppet, watch them with aide.
On Apr 20, 2013, at 12:05 PM, Singer Wang <w...@singerwang.com> wrote: Chef On Apr 20, 2013 12:00 PM, "Yves Dorfsman" <y...@zioup.com> wrote: > On 2013-04-20 07:45, Ali Sajid Imami wrote: > >> At $WORK, we tend to use a private git repository, and a custom script. We >> clone the directory to anywhere we like, commit our changes, then push it >> to >> github. Then a custom script, pulls all the stuff down and a puppet run >> puts >> the files in their appropriate place. >> >> > Using puppet just to copy known good file seems upside down! > > I like to: > > - use an deployment tool to create servers from fresh (ansible, puppet, > chef etc...). Never touch /etc on those servers, change your script, push. > > - cron rdiff-backup of /etc/ and other important directory the servers > that aren't under configuration management. > > > -- > Yves. > http://www.SollerS.ca/ > Unix/Linux and Python specialist in > Calgary. > > http://blog.zioup.org/ > ______________________________**_________________ > Tech mailing list > Tech@lists.lopsa.org > https://lists.lopsa.org/cgi-**bin/mailman/listinfo/tech<https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech> > This list provided by the League of Professional System Administrators > http://lopsa.org/ > _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
