On Wed, Apr 7, 2010 at 6:58 PM, Bruce Richardson <itsbr...@workshy.org> wrote: > On Mon, Apr 05, 2010 at 04:54:30PM +1000, Daniel Pittman wrote: >> >>> thank you so much for the reply. i have bunch of webserver, i want to >> >>> able >> >>> be able run svn update to all the webserver from master.
>> >> this is not what puppet specializes in. you can probably do it, but you will >> almost certainly find it more productive to use some alternate tool to >> implement this feature. I disagree. There's nothing wrong with doing this with Puppet, and we see this to be a very good way to deploy, for example, hosted apps and things that are traditionally hard to package. For instance, you can do a checkout at a specific git revision (I'm not positive the SVN module does this yet... but it should). Take a look at http://github.com/bruce/puppet-vcsrepo for a nice example of how to do this. If you can share other reasons why this doesn't work for you, or have additional ideas for improvements, let everyone know, and we can make it better. I don't see it desirable to manage the OS seperately from app deployments -- that's an incomplete model -- and our current limitation in this area is in modelling interactions /between/ servers. In the case of doing a simple SVN checkout, not a problem. And for the idea of gating conditions on external resources, we're making strides in that direction. http://github.com/reductivelabs/puppet-external-resource --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. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
