Ah that would explain things. I'll try running my Mojito app directly on 80 without nginx tonight! And I would just like to say what a delight developing with Mojito has been. Definitely a hidden gem. The team definitely needs to be more active in blogging about their recent progress.
Thanks @jesse, about blogging, we feel that it is almost there, we are making some big changes in the underlaying infrastructure (don't worry, we don't plan to break BC) to try to stabilize mojito/yui, then we plan to start blogging and try to grow are community.
P.S. feedback are welcome, any pain point, feature, enhancement, whatever, just feel free to open issues at:
Hi @jesse, yes, the string "started on http://127.0.0.1" in the mojito start message is just hard-coded. It binds to your system's loopback address using express/connect which in turn extend the built-in node http. Unfortunately it's not configurable from the cli.
From the docs, I think mojito's server should listen on any IP, and both 0.0.0.0:8666 and 127.0.0.1:8666 should work.. http://nodejs.org/api/http.html#http_server_listen_port_hostname_backlog_callback