I think you need a better definition of "dev". Are these machines that sysadmins will be using to develop files that will eventually be deployed with puppet? Or are these machines that you, as a sysadmin, are providing to a team of developers who perform application development?
If the former, then puppet probably shouldn't manage that file and you should keep it in source control. If the latter, then puppet probably shouldn't manage the file, but the developers should keep it in source control and deploy it as part of their software deployment plan when doing a release. Too often we refer to systems as "dev", when really from a sysadmin point of view they are production. Just because a developer is using them, it doesn't mean they can go down on a whim. That's what "dev" means from the sysadmin side. On Tue, Oct 21, 2008 at 4:49 PM, TomTom <[EMAIL PROTECTED]> wrote: > > Hello All, > I am trying to build up some dev boxes. These boxes are obviously > very different from our other production/QA environments. > > I have a need to allow developers to configure certain config files > such as httpd.conf. What I need to do is have puppet push out the > config file at installation and then allow the dev users to configure > it there after. > > Does anyone have a suggestion on how to implement this? > Thank you very much for your time! > -Tom > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
