Jeff,

Currently the rest keys are placed in /etc/xtuple/{org}/lib/rest-keys.

 if the rest keys can be shared amongst multiple organizations we could put
them in /etc/xtuple/lib/rest-keys  and share them which would be easier

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:38 AM, jgunderson <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
>
> OK, I thought you wanted support for this in install_bi.sh. If I make
> /etc/xtuple the default, what sub-folder do I use? See /etc/xtuple on
> pandora. Or are sub-folders not a production standard? From: Dave Cramer
> Sent: Thursday, December 26, 2013 9:28 AM To: xtuple/xtuple Cc: jgunderson
> Subject: Re: [xtuple] 21584, 22129 multiselect print support and reorganize
> config.js for pentaho (#1159 <https://github.com/xtuple/xtuple/pull/1159>)
> 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
> My point is that sample_config.js and the code should not make assumptions
> that are geared towards development. If anything the assumptions should be
> tailored to production. 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<https://github.com/xtuple/xtuple/pull/1>open source ERP community NextBusinessBlog.com <
> http://www.nextbusinessblog.com/> – Join the global innovation
> conversation … On Thu, Dec 26, 2013 at 9:23 AM, jgunderson <
> 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 This is not the production install.
> It follows the same pattern as install_xtuple.sh which does not use
> /etc/xtuple for the config.js file, etc. Separately, we could work on a
> project to make the dev and production environments more similar. From:
> Dave Cramer Sent: Thursday, December 26, 2013 8:58 AM To: xtuple/xtuple Cc:
> jgunderson Subject: Re: [xtuple] 21584, 22129 multiselect print support and
> reorganize config.js for pentaho ( #1159<https://github.com/xtuple/xtuple/pull/1159><
> https://github.com/xtuple/xtuple/pull/1159>) 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 The production install does not and
> won't put the keys in ./lib/rest-keys It will be putting them in
> /etc/xtuple/lib/rest-keys I think it is important to consider the
> production environment as the main goal, not the development environment —
> Reply to this email directly or view it on GitHub. — Reply to this email
> directly or view it on GitHub<
> https://github.com/xtuple/xtuple/pull/1159/files#r8556009> . — Reply to
> this email directly or view it on GitHub.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/xtuple/xtuple/pull/1159/files#r8556134>
> .
>