add bower config

[pourquoi]

then you need to run

bower register meteorserver git://github.com/visitsb/meteorserver

[pourquoi]

sorry it's bower register meteorserver git://github.com/visitsb/meteorserver.git

[visitsb]

@pourquoi thanks for the bower.json config. meteorserver is not yet ready as a node module, but there is plenty of scope (and interest) to do so. Your bower integration is definitely going to help in making that first step.

If I understand correctly, bower will only get the meteor.js but none of the server-side modules yet. Those are still left as a separate install. Only using bower will not get meteorserver up, and running.

Am I correct?

[pourquoi]

yes, it will only expose the content of public_html

this is usefull if you serve those files with nginx/apache instead of meteor

[visitsb]

@pourquoi thanks for clarifying.

meteorserver needs to obey same origin policy when serving javascript files out of public_html. That's mainly the reason why meteorserver channel can initiate push messages to callers without throwing browsers into security alert.

Having any other webserver today is not straightforward, unless some bridge is established to proxy meteorserver behind the scenes.

What I'll do is hold onto your bower.json, and work something towards enabling that as a single bower configuration that can work right out-of-the-box.