fix: Won't start when no config file specified on command line

Incorrect use of NODE_CONFIG_DIR and NODE_ENV environment variables

src/globals.js

@@ -87,10 +87,10 @@ if (options.configfile && options.configfile.length > 0) {
     }
 }
 
-// Set global variable conttaining the name and full pathof the config file
+// Set global variable conttaining the name and full path of the config file
 const configFile = path.join(
     process.env.NODE_CONFIG_DIR,
-    process.env.NODE_ENV + configFileExtension
+    `${process.env.NODE_ENV}.${configFileExtension}`
 );
 
 // Are we running as standalone app or not?
@@ -148,6 +148,13 @@ const logger = winston.createLogger({
     ),
 });
 
+// Show contents of environment variables controlling config file location and name
+logger.debug(`NODE_CONFIG_DIR: ${process.env.NODE_CONFIG_DIR}`);
+logger.debug(`NODE_ENV: ${process.env.NODE_ENV}`);
+
+// Output config file name and path to log
+logger.info(`Using config file: ${configFile}`);
+
 // Function to get current logging level
 const getLoggingLevel = () => logTransports.find((transport) => transport.name === 'console').level;