<div>
Interesting, thanks. I'd like to read that blogpost!</div>
<div></div>
<p style="color: #A0A0A8;">On Thursday, 20 October 2011 at 14:41, Thom May wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>We run bundle install --deployment as part of our CI process, and then<br>push out the results of CI as a tarball to our app servers.<br>I'm being hounded from various quarters to write a blog post about<br>this, so I might do that shortly.<br>-t<br><br>On Thu, Oct 20, 2011 at 14:38, Daniel Lucraft <<a href="mailto:dan.lucraft@gmail.com">dan.lucraft@gmail.com</a>> wrote:<br><blockquote type="cite"><div>Hi all,<br>question about the current Ruby Way. We're moving to Bundler, and it seems<br>the thing to do is to run "bundle install --deployment" when deploying,<br>which will install the gems from vendor/cache into vendor/bundle.<br>Fine. Except what do we do with native extensions? We're not wild about<br>having the compiler toolchain installed on all our appservers, partly for<br>security reasons.<br>Is there something obvious we're missing about how to deploy native<br>extensions with bundler?<br>thanks<br>Dan<br><br>__________________________<br>Daniel Lucraft<br><a href="http://danlucraft.com/blog">danlucraft.com/blog</a><br><a href="http://twitter.com/danlucraft">twitter.com/danlucraft</a><br><br>_______________________________________________<br>Chat mailing list<br><a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br><a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br></div></blockquote>_______________________________________________<br>Chat mailing list<br><a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br><a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br></div></div></span>
</blockquote>
<div>
<br>
</div>