FYI, these are the changes I needed to make to deploy subway to nodejitsu.
Note that the name and subdomain values in package.json must be modified for each deployment.
Also, jitsu writes updated package version numbers and an overall version number to the package.json as part of its deploy process. I didn't want to commit those, but am not sure if there's a better pattern for this (currently the file will have local modifications after a deploy). I did have to specify the 0.9.x-1 version of socket.io, because of a bug in jitsu that otherwise tries to load a typo-ed version: 0.9.x.-1.
make output of port at start be conditional on successful binding... …
…otherwise the failure is silenced
update package.json for nodejitsu deployability (jitsu will prompt to…
… update app, subdomain and version)
allow ENV variable to override port
update Readme to describe Nodejitsu deployment