I guess the issue with having a default is that it has to be set to
something. If it is left out of the deployed config.js it should error out.
And yes, the dev and production scripts need to be kept in sync. To wit,can
this https://github.com/xtuple/xtuple-scripts/pull/5 be merged?

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 Thu, Dec 26, 2013 at 9:31 AM, shackbarth <notifications@github.com>wrote:

> In scripts/install_bi.sh:
>
> > @@ -1,6 +1,6 @@
> >  #!/bin/sh
> >  RUN_DIR=$(pwd)
> > -LOG_FILE=$RUN_DIR/install_bi.log
> > +LOG_FILE=$RUN_DIR/instalLOG_FLl_bi.log
>
> I don't foresee the dev and production environments ever deploying to the
> same part of the filesystem. I agree with Dave that there doesn't need to
> be a dev bias baked into the code. I would go further and say that there
> also not be a prod bias baked into the code. So the only solution is to
> remove that default from the source altogether.
>
> I'm also inclined to update both the dev and prod script to insert the
> appropriate (different) row into config.js. Does anyone have any qualms
> with this? I realize that many core installs may not care where the keys
> are, but we have plenty of stuff in config.js that might not be relevant
> for all installs.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/xtuple/xtuple/pull/1159/files#r8556076>
> .
>