Don't put ENOS root directory under /tmp

[bmah888]

Don't put ENOS root directory under /tmp

[lomaxfrog]

Agree. I think the questions are:
1 - do we need a default directory, or, should ENOS just fail at boot time if ENOS_HOME is not defined ?
2 - if we decide on having a default directory, the current directory is almost just as bad as /tmp. The source directory would also be bad.

+1 to have ENOS fail if there is not defined ENOS_HOME, and remove all default (including in scripts)

[bmah888]

We need to be careful about this...ENOS_ROOT isn't the same as ENOS_HOME. I think we're both thinking about the root directory (where the data lives) as opposed to the home directory (where the code lives).

Anyways. We have the rootDirectory option in the configuration file to control this. Currently the default is /tmp/enos (and this in fact is how that directory gets defined on a fresh-out-of-the-box install). I can take the default out and force the admin / developer / whoever to define this in a configuration file. Or we can figure out some sensible default and put that in instead. (See base/enos.json.default for more details.)

The difference is if we do the former (no default), we're sacrificing the ability to run enos without any prior configuration. On the other hand if we do the latter (pick a default), that directory needs to be created by the admin before running ENOS for the first time anyway, so that still requires some effort. If we do the latter, at least they don't need to actually create enos.json, they just need to make the directory, so I'm gently leaning towards that direction.

I could go either way on this, and we can certainly change it later if we go one way and decide it didn't work.

[lomaxfrog]

Or, what we could do, is to define a default directory, prompt the user to accept or change it the first time it runs ENOS and the dir is not configured.