Merge pull request #4140 from silversword411/master

docs - adding google drive instructions
This commit is contained in:
Ylian Saint-Hilaire 2022-06-17 13:45:00 -07:00 committed by GitHub
commit 92cec5d16e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
8 changed files with 42 additions and 0 deletions

View File

@ -13,3 +13,6 @@ If you want to self-sign the mesh agent so you can whitelist the software in you
<div class="video-wrapper">
<iframe width="320" height="180" src="https://www.youtube.com/embed/qMAestNgCwc" frameborder="0" allowfullscreen></iframe>
</div>
!!!note
If you generate your private key on windows with use `BEGIN PRIVATE KEY` and openssl needs `BEGIN RSA PRIVATE KEY` you can convert your private key to rsa private key using `openssl rsa -in server.key -out server_new.key`

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 100 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 91 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 140 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 42 KiB

View File

@ -714,12 +714,19 @@ MeshCentral supports the local device group allowing devices that do not have an
![](images/2022-05-31-10-30-42.png)
To enable SSH support, add this line to the domain section of your config.json:
```json
"ssh": true
```
Video Walkthru
<div class="video-wrapper">
<iframe width="320" height="180" src="https://www.youtube.com/embed/TtW5-g6SeZQ" frameborder="0" allowfullscreen></iframe>
</div>
### Raritan and WebPowerSwitch with Relay
In addition to local device groups, the IP-KVM/Power switch device group was also improved to support a MeshAgent as a relay. This is big news for Raritan IP-KVM switch owners as you can now monitor your IP-KVM ports and access them remotely from the Internet. The same can be done with WebPowerSwitch allowing full out-of-band remote access to devices from anywhere in the world.
@ -1188,6 +1195,38 @@ mongorestore --archive=backup.archive
This will re-import the database from the backup. You can then start MeshCentral again.
### Backup to Google Drive
```bash
sudo systemctl stop meshcentral.service
nano /opt/meshcentral/meshcentral-data/config.json
```
Remove underscored items
![](images/2022-06-17-15-56-14.png)
```bash
sudo systemctl start meshcentral.service
sudo systemctl status meshcentral.service
```
Log into your MC:
![](images/2022-06-17-15-56-55.png)
![](images/2022-06-17-15-57-03.png)
Create desktop app
![](images/2022-06-17-15-57-15.png)
Enter the Client ID and Client Secret into MC
![](images/2022-06-17-15-57-30.png)
![](images/2022-06-17-15-57-52.png)
## HashiCorp Vault support
MeshCentral has built-in support for HashiCorp Vault so that all configuration and certificates used by MeshCentral are retrieved from a Vault server. Vault is a secret store server and when used with MeshCentral, the MeshCentral server will not be storing any secrets locally. You can get started with Vault here: https://www.vaultproject.io/