This addresses issue #6 by adding a log file to the main bot.js scrip…

…t, allowing for every command executed to be logged in a file, with a timestamp. This will allow the sysadmin to view the log file and see what commands have been issued.

bot.js

@@ -14,6 +14,7 @@ const config = require('./config.json');
 const configSecret = require('./config-secret.json');
 const db = require('./db');
 const fs = require('fs');
+const cmdLog = './cmdExec.log';
 
 // Set up the logger for debug/info
 const logger = require('winston');
@@ -64,6 +65,18 @@ try {
     client.deleteCallingCommand = false;
 }
 
+try {
+    var stream = fs.createWriteStream(cmdLog, {flags:'a'}); 
+    client.cmdLogStream = stream;
+    if(stream == null) {
+        logger.info(`Unable to initialise file stream for cmdExec.log`);
+    } else {
+        stream.write(new Date().toISOString() + ` bot started`) + `/n`;
+    }
+} catch (error) {
+    logger.info(`Unable to write ${cmdLog}`);
+}
+
 //
 // Set up the callback functions
 //
@@ -243,6 +256,21 @@ client.on('message', async message => {
                 client.myselfMaximum = 0;
             }
         }
+
+        if(client.cmdLogStream == null) {
+            logger.info("No open logfile stream");
+            client.cmdLogStream = fs.createWriteStream(cmdLog, {flags:'a'});
+        }
+        try {
+            nowDateTimeStr = new Date().toISOString();
+            logger.debug(`${nowDateTimeStr} - Writing to log file...`);
+            client.cmdLogStream.write(nowDateTimeStr + ':' + "\n");
+            client.cmdLogStream.write("    " + `executing ${cmd.name}` + "\n");
+            client.cmdLogStream.write("    " + `called by ${message.author.username}` + "\n\n");
+        } catch (e) {
+            logger.error(e);
+        }
+
         cmd.execute(message, args);
         if (client.deleteCallingCommand) {
             message.delete;