docs - Initial framework and layout

docs/docs/meshcentral/debugging.md

@@ -0,0 +1,105 @@
+Youtube video about  websockets: https://youtu.be/3vI4URd3VzU
+
+`Trace=1` as a parameter in chrome dev tools for debugging
+
+
+To log all database queries, change log_statement in /etc/postgresql/13/main/postgresql.conf
+
+```
+# CUSTOM
+log_statement = 'all'           # none, ddl, mod, all
+```
+
+The stacktrace was logged to `stdout/journalctl`. Supposedly, you can enable debug logging for node modules by adding `DEBUG=<modulename>` to the environment. 
+
+Adding this to `/etc/systemd/system/meshcentral.service` should do it but it didn't seem to do anything. 
+
+I think that's because Mesh uses the trace logging in the browser instead of logging things in the server logs. 
+
+```
+Environment=DEBUG=mesh*
+```
+
+If you want to change node to meshcentral in journalctl, add this to /etc/systemd/system/meshcentral.service.
+  
+```
+SyslogIdentifier=meshcentral
+```
+
+## Logging it all
+
+To log everything that's possible, prepare the log directory.
+
+```
+mkdir /meshcentral/meshcentral-logs/
+chown tactical:tactical logs
+ln -s ../meshcentral-logs/log.txt /meshcentral/meshcentral-data/log.txt
+```
+
+And then add this to your config.
+
+```json
+    "meshErrorLogPath": "/meshcentral/meshcentral-logs/",
+    "authLog": "/meshcentral/meshcentral-logs/auth.log",
+    "log": [
+        "cookie",
+        "dispatch",
+        "main",
+        "peer",
+        "web",
+        "webrequest",
+        "relay",
+        "webrelaydata",
+        "webrelay",
+        "mps",
+        "mpscmd",
+        "swarm",
+        "swarmcmd",
+        "agentupdate",
+        "agent",
+        "cert",
+        "db",
+        "email",
+        "amt",
+        "httpheaders",
+        "websocket"
+    ],
+```
+
+You'll then have 3 files:
+
+```bash
+-rw-rw-r-- 1 tactical tactical   2593 Feb  2 12:22 auth.log
+-rw-r--r-- 1 tactical tactical 147593 Feb  2 12:31 log.txt
+-rw-rw-r-- 1 tactical tactical    381 Feb  2 12:02 mesherrors.txt
+```
+
+And to make it truly log everything, change the following in meshcentral.js around line 3530.
+
+Old:
+```
+obj.fs.writeSync(obj.xxLogFile, new Date().toLocaleTimeString() + ' - ' + source + ': ' + Array.prototype.slice.call(...args).join('') + '\r\n');
+```
+
+New:
+
+```
+obj.fs.writeSync(obj.xxLogFile, new Date().toLocaleTimeString() + ' - ' + source + ': ' + args.join(' ') + '\r\n');
+```
+
+`log.txt` will now log everything in the Trace tab, but not formatted as nice.
+
+When doing debugging on my development server, I use this line in the settings section to block all agent connections except the agent I want:
+
+```
+"agentAllowedIp": [ "192.168.2.147" ],
+```
+
+Of course, this is just for debugging.
+
+
+## Finding system ID types
+
+<https://serverurl/meshagents>
+
+## General server statistics related

docs/docs/meshcentral/index.md

@@ -0,0 +1,9 @@
+# Meshcentral2 Guide
+
+[MeshCentral2 Guide](https://meshcentral.com/info/docs/MeshCentral2UserGuide.pdf)
+
+## Video Walkthru
+
+<div class="video-wrapper">
+  <iframe width="320" height="180" src="https://www.youtube.com/embed/D9Q7M7PdTg0" frameborder="0" allowfullscreen></iframe>
+</div>