Follow-up: If you are keen, please feel free to send a PR to the documentation repository <https://github.com/capistrano/capistrano.github.io> where we'd be happy to link to your article, I'm not sure the most appropriate place, but it looks like a great resource for people who need a hand to get the whole stack working.
Lee Hambley -- http://lee.hambley.name/ +49 (0) 170 298 5667 On 17 February 2014 17:47, Lee Hambley <lee.hamb...@gmail.com> wrote: > Thanks for taking the time to post this here, it's great to read: > > Capistrano <http://capistranorb.com/> was a perfect fit for all three of >> those items. It’s also well-known which is a bonus. And being based on Rake >> was an added benefit. > > > Basing our well known tool, on a well known tool (dependency resolution > driven!) was a massive gamble for the project. I only wish we had been able > to implement more of the workflow in a `build` fashion, rather than the > procedural method we have now. > > I also learned a few things about the Puppet ecosystem, which is alien to > me (being a Ruby guy, I tend towards Chef, for better or worse) > > For anyone interested, there's a post I wrote some time ago about how to > use Capistrano with Chef-Solo (my own most common use-case outside of > deploying Rails and Go apps) > http://lee.hambley.name/2013/06/11/using-capistrano-v3-with-chef.htmlwhich > includes some hints on how to speed things up using Rake's built-in > conditional rebuild of outdated targets (users of Make will thank me!) > > I think you might enjoy https://harrow.io/ when we launch, it'll be a > place to host your general purpose scripts, and share with your team, my > company has designed and built Harrow with this use-case in mind, although > our stack looks a little different (*ahem* *Chef*) - I'd be happy of the > chance to talk to you about that if you are ever interested. > > Thanks again! > > Lee Hambley > -- > http://lee.hambley.name/ > +49 (0) 170 298 5667 > > > On 16 February 2014 19:40, Joe Topjian <j...@topjian.net> wrote: > >> Hello, >> >> Lately I've been using Capistrano for infrastructure management. I've >> written some initial details here: >> >> >> http://terrarum.net/development/infrastructure-management-with-capistrano.html >> >> I thought this might be of interest because I usually see Capistrano used >> as a developer / code deployment tool rather than a sysadmin-focused tool. >> >> Joe >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Capistrano" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to capistrano+unsubscr...@googlegroups.com. >> To view this discussion on the web, visit >> https://groups.google.com/d/msgid/capistrano/6fa720b7-abf2-4c63-b091-498040677567%40googlegroups.com >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/CAN_%2BVLX9c37xYQ3kpCutL%3D6VkWXEE2mOws-i%2BY0_knx4RVnqeQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
