I like the idea of HTTP if it gets me closer to stubbing out the puppetmaster when I'm developing manifests. Thinking I could stand up a webrick server to resolve all the file sources. Of course, I'd use Apache or Nginx in production.
J. 2009/7/1 Marc Fournier <marc.fourn...@camptocamp.com>: > > > Hello, > >> I've been looking into having Puppet deploy some larger files and I'm >> noticing that it ties up puppetmasters quite a bit and can often >> result in a timeout if the file is too large. Before I submit a >> feature request for a http method for file sources, I would throw it >> out to the group and see if anyone had any thoughts on it. >> >> [...] > > I'm convinced we could benefit from having other file sources than > file:// and puppet://. There already is a (similar) ticket for this: > http://projects.reductivelabs.com/issues/184 > > You might also be interested by Luke Kanies's reply to more or less the > same question on puppet-dev a few weeks ago: > http://groups.google.com/group/puppet-dev/browse_thread/thread/275658354cd45bab/60b7672fbc35c371 > > I've started working on this (but unfortunately got preempted and now > stalled). It shouldn't be too difficult to implement, but as far as I'm > concerned, my knowledge of ruby is currently too low to do this > efficiently :-( > > Marc > > > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
