AFAIK process.env.PORT (what your Node.js app should listen on), is routed to port 80 for your Heroku app.
I have something like this - var port = process.env.PORT || 5000; So on Heroku it's what ever is assigned it listens on but publicly it's 80 and 5000 on development. Regards, Andrew On 3 Jan 2012, at 19:18, Steve wrote: > I plan to run it on port 80, so it can run behind block firewall. > > On Dec 30 2011, 12:58 pm, Daniel Huckstep > <[email protected]> wrote: >> You can't use websockets on Heroku. Their networking stack doesn't work >> with WS yet, but to my knowledge it's a problem they are trying to solve. >> >> Everything starts at port 80, but your app server is running on whatever >> port it gets told to by the Heroku infrastructure so that requests can get >> properly routed. Unless I'm missing something, there's nothing special >> about that example that requires the actual node app server to be running >> on port 80. >> >> - Daniel > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
