-
Notifications
You must be signed in to change notification settings - Fork 0
Servers
Most people deploy JRuby applications using typical Java application servers like Tomcat or JBoss. When using these servers, the usual solution is Warbler. Warbler bundles up any Rack-based application into a Java "Web Application aRchive" (WAR) file, which can then be deployed on any web application server.
The following is a list of servers known to work with JRuby. It is not meant to be exhaustive.
- Tomcat
- JBoss
- GlassFish
- WebLogic
- WebSphere
The usual Ruby way to run a server is to launch a small command-line server pointing at the application directory. Some of the standard Ruby servers work with JRuby, and an additional set of servers have been built specifically for JRuby by either wrapping an existing server or by simply wrapping Java libraries.
The following is a list of embedded/micro/commandline servers for JRuby. If you don't see your favorite here, add it!
- Trinidad - A wrapper around Tomcat.
- Mizuno - A wrapper around Jetty.
- Kirk - Another Jetty wrapper, but less "micro" with redeploy and multiple appsupport.
- Aspen - A server based on Netty, a Java NIO framework.
- TorqueBox - A server based on JBoss AS.
- Mongrel - The classic Ruby server, no longer maintained.
- GlassFish gem - A gem-borne embedded version of GlassFish, now no longer maintained by Oracle.
There are also several cloud and hosting services that either directly support JRuby or implicitly support it by having general Java webapp support.
The following services are known to work. Other webapp services should generally support JRuby applications (via Warbler) as well.
- Engine Yard - Direct support, generally available now.
- Google AppEngine - Indirect support, but a community exists around JRuby deployment
- Amazon Elastic BeanStalk - An elastic Java webapp cloud from Amazon based on Tomcat.