Barry Jones brightball

#Mac OS X

Apps

With Heroku's JRuby support you may have already seen that you can run TorqueBox Lite on Heroku. But, that only gives you the web features of TorqueBox. What about scheduled jobs, backgroundable, messaging, services, and caching?

With a small amount of extra work, you can now run the full TorqueBox (minus STOMP support and clustering) on Heroku as well! I've successfully deployed several test applications, including the example Rails application from our Getting Started Guide which has a scheduled job, a service, and uses backgroundable and messaging.

This example uses TorqueBox 3.0.2, but the instructions may work with other TorqueBox versions.

Steps Required

Create a JRuby application on Heroku, or convert an existing application to JRuby. Make sure your application works on JRuby on Heroku before throwing TorqueBox into the mix.
Add th

#Overview drip is an awesome command line tool that can be used to dramatically lower perceived JVM startup time. It does this by preloading an entirely new JVM process\instance and allowing you to simply use the preloaded environment. This has extraordinary results with jruby.

We reduced time to run rake environment from 13 seconds to a mere 3.5 seconds. This is actually at or near MRI 1.9.3p327 (with falcon patch) speeds!

Adding a few addition jruby options will reduce startup time even further (down to 1.69 seconds).

#Install Drip Install drip if you haven't already (see https://github.com/flatland/drip)

SSH agent forwarding and screen

When connecting to a remote server via SSH it is often convenient to use SSH agent forwarding so that you don't need a separate keypair on that server for connecting to further servers.

This is enabled by adding the

ForwardAgent yes

option to any of your Host entries in ~/.ssh/config (or alternatively with the -A option). Don't set this option in a wildcard Host * section since any user on the remote server that can bypass file permissions can now als use keys loaded in your SSH agent. So only use this with hosts you trust.

	class BackgroundSessionProxy < Sunspot::SessionProxy::AbstractSessionProxy
	class <<self
	def async?
	!!Thread.current[:background_session_proxy_async]
	end

	def with_async
	self.async = true
	begin
	yield

	# Some good references are:
	# http://russbrooks.com/2010/11/25/install-postgresql-9-on-os-x
	# http://www.paolocorti.net/2008/01/30/installing-postgis-on-ubuntu/
	# http://postgis.refractions.net/documentation/manual-1.5/ch02.html#id2630392

	#1. Install PostgreSQL postgis and postgres

	brew install postgis
	initdb /usr/local/var/postgres
	pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log start

	require "rubygems"
	require "twitter"
	require "json"

	# things you must configure
	TWITTER_USER = "your_username"
	MAX_AGE_IN_DAYS = 1 # anything older than this is deleted

	# get these from dev.twitter.com
	CONSUMER_KEY = "your_consumer_key"

	#! /bin/bash

	array=( $@ )
	len=${#array[@]}
	app=${array[$len-1]}
	args=${array[@]:0:$len-1}

	buffer_file=/tmp/last_heroku_run_`date +%N`

	/usr/bin/heroku run "$args; echo \$?" --app $app 2>&1 \| tee $buffer_file

	if [[ $BUILD_STATUS == "success" ]]
	then
	export STATUS="success"
	else
	export STATUS="failure"
	fi

	curl "https://api.github.com/repos/justincampbell/my_repo/statuses/$GIT_COMMIT?access_token=abc123" \
	-H "Content-Type: application/json" \
	-X POST \

	<!DOCTYPE html>
	<html>
	<head>
	<script src="//code.jquery.com/jquery-1.9.1.min.js"></script>
	<script src="//cdnjs.cloudflare.com/ajax/libs/handlebars.js/1.0.0-rc.3/handlebars.js"></script>
	<script src="//cdnjs.cloudflare.com/ajax/libs/ember.js/1.0.0-rc.3/ember.js"></script>
	<script src="//maps.googleapis.com/maps/api/js?sensor=false"></script>
	</head>
	<body>
	<script>