Are you saying rather then store the actual configuration files in version control, store everything that is necessary to generate the configuration file in version control?
Thanks, ~Jet On Thu, Nov 27, 2008 at 9:11 AM, Mike Renfro <[EMAIL PROTECTED]> wrote: > > Jet wrote: > >> We are looking to find something to manage our configuration files. >> Specifically our Apache web server farm configuration files. We would >> like to store them in version control and have puppet push them out >> or have the clients pull them making the necessary customizations for >> each physical machine. > > Not contradicting anything said before, but yes, puppet can handle that. > Rather than keep a separate copy of each server's configuration file in > version control, you'll possibly want to keep a template of the > configuration files in version control, and let the puppetmaster server > customize those templates for each server as needed. Early on, you'll > probably want to switch from making piecemeal puppet classes to making > self-contained modules that contain all the files, templates, and puppet > manifests to configure a particular service. > > Example of such a module for Amanda is at > http://blogs.cae.tntech.edu/mwr/2007/08/02/the-new-file-server-puppet-and-modules/ > -- not trivially simple, but not too complex, either. > > -- > Mike Renfro / R&D Engineer, Center for Manufacturing Research, > 931 372-3601 / Tennessee Technological University -- [EMAIL PROTECTED] > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
