|
My current apps architecture is using Node.js as the front facing server receiving the initial request from users. I look at the requested URL and if it's one used for long polling I handle it in Node.js, otherwise I pass off the request to Apache/Django. On my local machine I do this by attaching node.js to port 8080 and django dev server to 8000. I am wonder how I cold possibly do this on a webfaction server? It seems like each app is only given one port to use. I am also doing inter-process communication between the Node.js app and the Django app over sockets, which requires another port. Any ideas on how to implement this on webfaction? Thanks, Jonathan |
|
As long as you can make your application listen on a specified port you may create a "custom application" to be assigned a port for local communication or to be forwarded like any other HTTP app with the control panel. If you need a specific port or external, non-HTTP traffic on the port than you may purchase an dedicated IP address. Our documentation on this may be found here, http://docs.webfaction.com/software/custom.html#custom-applications |
