docs - fixing json formatting
silversword411 committed
May 23, 2022 at 22:36 UTC
2139375d5532a09b0956eba448b7bfa7b3ce89c3
1 file changed
+5
-5
docs/docs/meshcentral/index.md
+5
-5
@@ -715,7 +715,7 @@ Let’s get started by configuring MeshCentral with the following values in conf
715
```json
716
{
717
"settings": {
718
- "Cert": "myservername.domain.com"
718
+ "Cert": "myservername.domain.com",
719
"Port": 4430,
720
"AliasPort": 443,
721
"RedirPort": 800,
@@ -889,7 +889,7 @@ First we will start with the MeshCentral configuration, here is a minimal config
889
```json
890
{
891
"settings": {
892
- "Cert": "myservername.domain.com"
892
+ "Cert": "myservername.domain.com",
893
"Port": 4430,
894
"AliasPort": 443,
895
"RedirPort": 800,
@@ -1019,7 +1019,7 @@ On the MeshCentral side, we are not going to use port 80 and need the main HTTPS
1019
```json
1020
{
1021
"settings": {
1022
- "Cert": "myservername.domain.com"
1022
+ "Cert": "myservername.domain.com",
1023
"Port": 444,
1024
"AliasPort": 443,
1025
"RedirPort": 0,
@@ -1601,8 +1601,8 @@ In this annex, we present a complete sample config.json file. You would put this
1601
"UserQuota": 1048576,
1602
"MeshQuota": 248576,
1603
"NewAccounts": true,
1604
- "Footer": "<a href='https://twitter.com/mytwitter'>Twitter</a>"
1605
-"PasswordRequirements": { "min": 8, "max": 128, "upper": 1, "lower": 1, "numeric": 1, "nonalpha": 1 }
1604
+ "Footer": "<a href='https://twitter.com/mytwitter'>Twitter</a>",
1605
+ "PasswordRequirements": { "min": 8, "max": 128, "upper": 1, "lower": 1, "numeric": 1, "nonalpha": 1 }
1606
},
1607
"customer1": {
1608
"Dns": "customer1.myserver.com",