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)

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.