Rob Hirschfeld ([email protected]) wrote: > John, > > My sense on this is that gems are more for Rails extensions (parts > of apps) than a full application. While OpenCrowbar is mostly > Rails, it is NOT only Rails. There's quite a bit of extra stuff > (chef, erlang, scripts, docs, etc) that we package at the same level > as the Rails app.
Agreed, that's why I proposed wrapping gems inside native packages (.debs / .rpms). Then you get the best of both worlds. > I found this link that supports this: > https://groups.google.com/forum/#!topic/puppet-users/aVTPAfcVBcE That thread is short on details. As you would hope from a company whose core business involves packaging software, SUSE has a lot of experience in this area ;-) and it's a complicated topic with lots of pitfalls. Here's a great presentation that Tim Serong (one of our engineers who sometimes hacks on Crowbar / OpenStack, and who some of you may have met in Hong Kong) made a few months ago, on the topic of packaging and deploying Rails apps: http://ourobengr.com/2013/10/tied-to-the-rails/ There's also https://en.opensuse.org/openSUSE:Ruby_Gem_Strategies which is a working document I compiled a while ago (motivated by our work in packaging Crowbar) which is somewhat openSUSE-centric but may still be of use. Neither contains silver bullets, but as you can see it's a tricky topic which we have put a lot of thought into over the last ~2 years. _______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
