#377 Trinidad pro

Trinidad is designed to serve JRuby web applications and gives you the power of Java while still keeping the feel of traditional Rails deployment. Here I show how to setup a Capistrano recipe, configure it, and more.

Ryan did not mention this explicitly, but it might not be obvious to some: You do not have to "deal" with Capistrano + JRuby 1.7 issues (Highline, SSH Forwarding). It's perfectly fine to use MRI while invoking the cap commands on your machine, you "only" need JRuby on the remote server where Trinidad lives.

One might also consider using the current "stable" version of JRuby on production 1.6.7 if you run into any specific issues with 1.7 (it's still a preview version although pretty stable).

Is anyone using a JRuby server for their production sites just out of curiosity? I've seen some impressive benchmarks for JRuby servers like Puma (https://github.com/czarneckid/puma-benchmarking and http://puma.io/), but in my personal testing I usually found it to be around par with MRI Servers like Thin. I assume there's some additional configuration for JVM to achieve those results.

Are you using nginx with Trinidad? If so, you would set up the SSL on nginx and ensure that external traffic is not accepted on the port that nginx is forwarding traffic to Trinidad. On ubuntu, you would do this through ufw or iptables.

Traffic between nginx and trinidad would be loopback, so you shouldn't need an SSL unless you are forwarding to a separate server.