MyFavMirrors/MeshCentral
1
0
Fork 0
mirror of https://github.com/Ylianst/MeshCentral.git synced 2025-02-04 10:25:58 -05:00
Code Issues Packages Projects Releases Wiki Activity

docs - understanding node and paths https://github.com/Ylianst/MeshCentral/issues/4379

Browse Source
This commit is contained in:
silversword411 2022-08-10 13:58:48 -04:00
parent a3f1c0fa24
commit 730bcb034e
No known key found for this signature in database
GPG Key ID: CF805301BBB8CC0C
1 changed files with 31 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
docs/docs/meshcentral/debugging.md
View File

@ -21,6 +21,37 @@ Make sure you understand how MeshCentral works with your browser using chrome de
"AgentWsCompression": false, "AgentWsCompression": false,
``` ```
### Understanding node and paths
Note that when running MeshCentral, you should always run like from the path that is parent to node_modules, so you do this:
```
cd C:\Program Files\Open Source\MeshCentral
node node_modules\meshcentral
```
You do NOT do this:
```
cd C:\Program Files\Open Source\MeshCentral\node_modules\meshcentral
node meshcentral
```
The problem with the second command is that NPM may install missing modules are the incorrect location.
Also, in general I recommend not using the MeshCentral MSI Installer and just install manually unless you are very much scared of the command prompt. Anyone that knows about bit about the shell should install MeshCentral like this:
```
mkdir c:\meshcentral
cd c:\meshcentral
npm install meshcentral
node node_modules\meshcentral
(ctrl-c when done installing optional modules)
node node_modules\meshcentral --install
```
This way, just have a lot more control over what is going on. Just my opinion, the MSI installer basically does the same thing and installs NodeJS for you.
### Unable to update server ### Unable to update server
Generally the problem is that MeshCentral can't find the npm tool and so, can't run it to see if there is a new version. You can fix this by setting the path to npm in the config.json like this: Generally the problem is that MeshCentral can't find the npm tool and so, can't run it to see if there is a new version. You can fix this by setting the path to npm in the config.json like this: