This seems like a pretty invasive change to fix "node not found" This
impacts production environments as I think it is prudent to keep all of the
various components exactly the same between development and production so
as to not have to go searching for bugs caused by unknown differences
between different packages. If there is a bug in a specific version of a
component I can see committing the resources to changing and testing
production setups. Was there a bug in a component that precipitated this
change ?

Dave Cramer
Senior Enterprise Architect
+1-757-461-3022x130
davec@xtuple.com
xTuple.com <http://www.xtuple.org/>  <http://www.xTuple.org>– Download FREE
PostBooks ERP, CRM, accounting software
xTuple.org <http://www.xtuple.org/> – Contribute to World’s #1 open source
ERP community
NextBusinessBlog.com <http://www.nextbusinessblog.com/> – Join the global
innovation conversation


On Sat, Dec 7, 2013 at 2:50 PM, Travis Webb <notifications@github.com>wrote:

> In README.md:
>
> >
> >      cd node-datasource
> > -    sudo ./main.js
> > +    node main.js
> >
> >  Launch your local browser and navigate to the address `localhost`. Default username and password are `admin`.
>
> you're right, I'll add the :8443
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/xtuple/xtuple/pull/1130/files#r8182511>
> .
>