On Tue, Mar 10, 2009 at 1:28 PM, thomas <thomas.bik...@gmail.com> wrote: > > Hello, > > I was evaluating the use of the puppet with the single purpose to > generate a handful of httpd.conf files for several apache instances. > Unfortunately my deployment environment is very restrictive and I can > not use puppetd on the target hosts - I wanted however take advantage > of puppet DSL to describe the system (few dozen of instances with ever- > changing ports) and generate stuff I need on the external box, > deploying configuration via ssh afterwards on the clients. > > If someone has faced similar situation - what pointers would you > suggest? >
I believe I would do the following: I would skip the needing for apache in this case. the out of the box puppetmaster runs a webbrick that runs on port 8141 and seems to cover what you are looking for. In this case, you are wanting to make sure that it only listens/talks on 127.0.0.1 and then sync out the puppet directories. -- Stephen J Smoogen. -- BSD/GNU/Linux How far that little candle throws his beams! So shines a good deed in a naughty world. = Shakespeare. "The Merchant of Venice" --~--~---------~--~----~------------~-------~--~----~ 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 puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
