Look into Bundler, especially the 'bundle install --deployment' option. I package my app into a binary artifact (using .deb, as we run on Ubuntu), and then no internet access is required to bundle install and start the app server.
The caveat is, I don't know what differences there are (if any) with JRuby. Would you package as a .WAR file? How does Bundler work? These are the things you should figure out. I would be quite interested if you could post back here with your solution! On 16 January 2015 at 16:01, Chason Choate < chason.cho...@digitalreasoning.com> wrote: > I have an interesting use case for Rails and I would greatly appreciate > this community's opinion on the matter. > I'm curious if it's possible to build a Rails app that can accomplish the > following: > > Environment stipulations > ------------------------------------------------------------- > > * Must run on the JVM so JRuby. > * The app will not have internet access in production. (We still have > build servers that can package gems) > > Ideal functionality > ------------------------------------------------------------- > > * The main Rails app should be able to support a variable amount of > engines. > * I have played with this and it can be done by tweaking the Gemfile > to load the engines. > * Downside is we now have to disregard the Gemfile.lock to accommodate > additional engines being added at any time. > * Engines should be drop-in ready. > * The engines should come packaged with all the gems they need to run. > * There should be no additional installing steps after dropping in an > engine. > * That means no 'bundle install' or anything else. > > So my major concern at the moment is with the gems. When I drop in an > engine and restart the server is there a way bundler can pick up the > packaged gems within the engine without any install step? Maybe playing > with the GEM_PATH or something? Anyway I would like to hear your opinions > and see if we can figure something out. Thanks for checking this out! > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rubyonrails-talk+unsubscr...@googlegroups.com. > To post to this group, send email to rubyonrails-talk@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/rubyonrails-talk/b3cacb4f-88b2-434c-8973-f9701ac25c2f%40googlegroups.com > <https://groups.google.com/d/msgid/rubyonrails-talk/b3cacb4f-88b2-434c-8973-f9701ac25c2f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CABLJ1DJjbEWWpboCMvbR8Rb%2BVMOSjpuFziVG%3DBRO43uv0hCXMg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
