[LRUG] Compiling native extensions during deployment?

[Thom May]

(oh, this of course assumes that all your boxes are the same
architecture, which makes life a bit interesting on AWS right now what
with 32bit only small instances)

On Thu, Oct 20, 2011 at 14:41, Thom May <thom at may.lt> wrote:
> We run bundle install --deployment as part of our CI process, and then
> push out the results of CI as a tarball to our app servers.
> I'm being hounded from various quarters to write a blog post about
> this, so I might do that shortly.
> -t
>
> On Thu, Oct 20, 2011 at 14:38, Daniel Lucraft <dan.lucraft at gmail.com> wrote:
>> Hi all,
>> question about the current Ruby Way. We're moving to Bundler, and it seems
>> the thing to do is to run "bundle install --deployment" when deploying,
>> which will install the gems from vendor/cache into vendor/bundle.
>> Fine. Except what do we do with native extensions? We're not wild about
>> having the compiler toolchain installed on all our appservers, partly for
>> security reasons.
>> Is there something obvious we're missing about how to deploy native
>> extensions with bundler?
>> thanks
>> Dan
>>
>> __________________________
>> Daniel Lucraft
>> danlucraft.com/blog
>> twitter.com/danlucraft
>>
>> _______________________________________________
>> Chat mailing list
>> Chat at lists.lrug.org
>> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>>
>>
>