Derby on Heroku port binding

[Robert]

*Almost* have Derby up and running on Heroku, but I'm getting some port binding errors in the logs. Wondering where I change port info in Derby.js Only thing I'm seeing in the documentation about ports is under stores. Any info on how to set this?

Here's the error (in bold) in the Heroku logs:

2012-06-03T20:27:12+00:00 heroku[web.1]: Starting process with command `node server.js`

2012-06-03T20:27:13+00:00 app[web.1]: Go to: http://localhost:3000/

2012-06-03T20:27:13+00:00 app[web.1]: info: socket.io started

2012-06-03T20:27:13+00:00 app[web.1]: `kill -s SIGUSR2 1` to force cluster reload

2012-06-03T20:27:13+00:00 app[web.1]: Starting cluster with 1 workers in undefined mode

2012-06-03T20:27:14+00:00 heroku[web.1]: Error R11 (Bad bind) -> Process bound to port 3000, should be 6302 (see environment variable PORT)

2012-06-03T20:27:14+00:00 heroku[web.1]: Stopping process with SIGKILL

2012-06-03T20:27:15+00:00 heroku[web.1]: Process exited with status 137

2012-06-03T20:27:15+00:00 heroku[web.1]: State changed from starting to crashed

As you can see, Heroku is telling me to check the "environment variable PORT," but I thought I'd also post this here in case anyone had any clue...Thx!

[Robert]

Follow up:

Here's the Heroku error documentation. Not very helpful. :(

https://devcenter.heroku.com/articles/error-codes#r11__bad_bind

[László Bácsi]

Here's how you can set the port in server.js:

require('derby').run(__dirname + '/lib/server', process.env.PORT || 3000)

Best,

LacKac

[Robert]

Brilliant, thank you that worked. Future ref for others, the port is passed by Heroku with an environment variable: https://devcenter.heroku.com/articles/nodejs#write_your_app

[Kyle Finley]

Robert,

If you need more any more guidance, here's an attempt that I made to create a blog using derby.

https://github.com/scotch/derby-blog

http://derby-blog.herokuapp.com/

I was able to get it running on heroku, but I got stuck on some of the model behavior, so I temporarily abandoned it. One of the major issue I had with heroku was the "cold start" time. If the instance was shutdown it would take up to 30 seconds to restart, which didn't work for my needs.

I hope it helps,

- Kyle

[Robert]

Thanks, Kyle.