Merge pull request #1168 from gatos-jd/20190408/config-file-behavior

Changing startup behavior around config file

Author: jaxoncreed

bin/lib/cli-utils.js

@@ -1,5 +1,5 @@
 const fs = require('fs-extra')
-const { cyan, bold } = require('colorette')
+const { red, cyan, bold } = require('colorette')
 const { URL } = require('url')
 const LDP = require('../../lib/ldp')
 const AccountManager = require('../../lib/models/account-manager')
@@ -41,7 +41,22 @@ function loadConfig (program, options) {
     const config = JSON.parse(file)
     argv = { ...config, ...argv }
   } catch (err) {
-    // No file exists, not a problem
+    // If config file was specified, but it doesn't exist, stop with error message
+    if (typeof argv['configFile'] !== 'undefined') {
+      if (!fs.existsSync(configFile)) {
+        console.log(red(bold('ERR')), 'Config file ' + configFile + ' doesn\'t exist.')
+        process.exit(1)
+      }
+    }
+
+    // If the file exists, but parsing failed, stop with error message
+    if (fs.existsSync(configFile)) {
+      console.log(red(bold('ERR')), 'config file ' + configFile + ' couldn\'t be parsed: ' + err)
+      process.exit(1)
+    }
+
+    // Legacy behavior - if config file does not exist, start with default
+    // values, but an info message to create a config file.
     console.log(cyan(bold('TIP')), 'create a config.json: `$ solid init`')
   }