Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to (sort of) mimic the server setup of the official Meteor deploy infrastructure (the * subdomain deployments).

If it's only a handful of known meteor apps, I can just run the bundled apps on different ports and use nginx proxying. But how can I accommodate an arbitrary number of meteor app deployments on a single server (just like the official one)?

Thanks for the help!

share|improve this question
up vote 1 down vote accepted

just use node-http-proxy and either use the command line or restart the proxy process on changes.

share|improve this answer
looks like i'll be using it – Dave Jan 28 '13 at 23:31

I would recommend HAProxy (or NginX) over node-http-proxy unless you need custom behaviour.

Both HAProxy and NginX perform better than node-http-proxy, and have much lower memory consumption.

Also, node-http-proxy (or just Node.js in general) is terrible at serving over SSL... So, if you go that route, make sure to terminate SSL before Node.js.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.