stackdump stackdump

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

Auto-deploying built products to gh-pages with GitHub Actions

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.

A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:

It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
It is free, with no quotas.
Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.

	#
	# This config file is a combination of ideas from:
	# http://www.37signals.com/svn/posts/1073-nuts-bolts-haproxy
	# http://www.igvita.com/2008/05/13/load-balancing-qos-with-haproxy/
	# http://wiki.railsmachine.com/HAProxy
	# http://elwoodicious.com/2008/07/15/nginx-haproxy-thin-fastcgi-php5-load-balanced-rails-with-php-support/
	# http://upstream-berlin.com/2008/01/09/using-haproxy-with-multiple-backends-aka-content-switching/
	# http://wiki.railsmachine.com/HAProxy
	# http://gist.github.com/raw/25482/d39fb332edf977602c183194a1cf5e9a0b5264f9
	#

	/** @jsx React.DOM */
	var MyComponent = React.createClass({
	render: function() {
	// Defaults in case the props are undefined. We'll have a solution for this
	// soon that is less awkward.
	var perMinute = this.props.perMinute \|\| '-';
	var perDay = this.props.perDay \|\| '-';
	return (
	<div>
	<h3>Clickouts</h3>

	@angular.module('HelloApp', ['components'])

	@angular.module('components', [])
	.directive('testElem', ->
	restrict: 'A'
	template: '<div class="my-directive-class"><h1>Hello...</h1><p ng-repeat="obj in arr">{{obj}}</p></div>'
	link: (scope, iterStartElement, attr) ->
	$(".my-directive-class").css({ 'background-color': 'yellow'})
	scope.arr = ["Steve", 'is', 'the', 'beast']
	)

	function git() {
	GIT_CMD=`which git`
	$GIT_CMD "$@"
	status="$?"
	[[ $status = 0 ]] \|\| return $status

	for opt in "$@"; do
	case "$opt" in
	commit \| rebase)
	$GIT_CMD ctags

	bit = require "bit"
	ev = require "ev"

	ltn12 = require "ltn12"
	socket = require "socket"

	-- make protect and newtry coroutine friendly
	socket.protect = (fn) -> fn
	socket.newtry = (finalizer) ->
	(...) ->

	#cloud-config

	coreos:
	etcd:
	# generate a new token for each unique cluster from https://discovery.etcd.io/new
	discovery: https://discovery.etcd.io/<token>
	# multi-region deployments, multi-cloud deployments, and droplets without
	# private networking need to use $public_ipv4
	addr: $private_ipv4:4001
	peer-addr: $private_ipv4:7001

	#!/usr/bin/env python
	"""
	Starts a Tornado static file server in a given directory.
	To start the server in the current directory:

	tserv .

	Then go to http://localhost:8000 to browse the directory.

	Use the --prefix option to add a prefix to the served URL,