I spent some time trying to get EB to work with Rails. The sticking point for me was that it insisted on doing a full Gems download every time you started a server. This was taking more than ten minutes. Which means that "live failover" -- kind of the point of using EB -- fails.
You can't really vendor gems because binary ones are built on a different architecture, so I guess it has to do this. I got into discussing ways of having a "build" machine on EC2, and then hacking the startup script so it downloaded the Gems from that machine, but it was all a bit house of cards for me. Fortunately, you can get the live failover and suchlike from a straight-up EC2 instance, so I'm just doing that. On Aug 11, 2014, at 17:00 , Jason Liebrecht <[email protected]> wrote: > Hello, > I've been around for a while but just haven't had much to say :-) > > I'm wondering if anyone has any experience doing Elastic Beanstalk deploys on > Ruby Apps. I've been mucking with this for three days now. Server will come > up, as soon as I update with the app I get failures all over the place and > don't even know where to start. If I manually set everything on a server, it > works ok but ideally I'd like to just be able to take advantage of the > scaling should we need it. > > I'm willing to pay, not looking for freebees. Let me know! > > Experience deploying AngularJS apps is a bonus. > > Jason > > -- > email: [email protected] > > > -- > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > --- > You received this message because you are subscribed to the Google Groups "SD > Ruby" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
