> > > Can you share some examples of where your dividing line is and some of > the tasks that are hard to handle in Puppet today? >
Here's how it worked: http://www.build-doctor.com/2009/12/09/dependency-hell/ Mainly, it was there to complement the lack of Rubygem dependencies, but it meant that there was a way for developers to maintain crontabs. We used Passenger and Rails so there wasn't much need to do anything else. I could have checked that there were processes running but the hosting peeps already had Monit. > > Ideally I'd like to figure out how to incorporate more of that into > puppet-core. Bruce has been working on a version control type, that > could be used to check sources > out of version control and eliminate some packaging needs for hosted > apps, though I'm curious as to what other niches might not be covered. > I've considered this for about ten seconds, but how about supporting some deployment tools in Puppet? So you could write a recipe that deploys middleware, application and other infrastructure for example. J. > --Michael > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
