Add updates for v0.6.3

Author: ohsayan

docs/5.cfg-files.md

@@ -14,6 +14,7 @@ A configuration file is a TOML file, which has the following basic structure:
 host = "127.0.0.1"
 port = 2003
 noart = false # optional
+maxcon = 50000 # optional
 
 [bgsave]
 enabled = true
@@ -27,6 +28,7 @@ advanced configuration:
   - `host` : This is the IP address to which you want the database server to bind to. It can be any valid IPv4 _or_ IPv6 address, as a quoted string
   - `port` : This is the port to which you want Sky to bind to
   - `noart`: This is **an optional argument** and is recommended for secure environments where displaying terminal artwork might cause problems
+  - `maxcon` : Set the maximum number of clients that can query concurrently
 - `bgsave`:
   - `enabled`: This is an optional key, which is to be set to true to enable BGSAVE or false to disable it. If this key is not specified, Sky will enable BGSAVE by default
   - `every` : Run BGSAVE `every` seconds. So, for example, if you set this to 120, BGSAVE will run every two minutes. This is also an optional key, and if you don't provide it, the default BGSAVE duration of 120 seconds is used

docs/deployment-notes.md

@@ -9,7 +9,12 @@ Here are some _good to know_ things about deploying Skytable:
 - The daemon will create a `.sky_pid` file in its working directory which functions as a PID file
   and indicates other processes to not use the data directory. If the daemon is somehow forcefully
   stopped, the file may not be removed. In that case, you should manually remove the file
-- Skytable currently has a hardcoded limit of 50000 connections on a single daemon instance. This limit will be user accessible in the (near) future
+- Skytable currently has a default limit of 50000 connections on a single daemon instance. This limit
+  can be modified by setting the `maxcon` in the [configuration file](config-files).
+  :::note
+  Make sure you change `maxcon` according to the available system resources to avoid attacks
+  that may cause your system to crash
+  :::
 - Skytable is inherently multithreaded. As of now, there is no way to stop Skytable from using
   multiple threads
 - The best way to deploy Skytable is as a service (and passing `--noart` to avoid terminal artwork

docs/ssl.md

@@ -8,7 +8,7 @@ Skytable lets you secure connections with TLS/SSL. This feature is built into Sk
 
 This is outside the scope of this document, but you can read [this guide on Stackoverflow](https://stackoverflow.com/a/10176685) to get a brief idea of creating one.
 
-### Step 2: Add this to your configuration and launch
+### Step 2: Add it to your configuration and launch
 
 #### With config files
 Add the following block:
@@ -30,4 +30,13 @@ skyd -z cert.pem -k key.pem
 ```
 :::tip Tip
 You can pass the `--sslonly` flag to force the server to only accept secure connections, disabling the non-SSL interface. When this flag is not passed, and other SSL options are given — the server listens to both SSL and non-SSL requests
-:::
+:::
+
+:::info Note
+To use TLS with the Skytable shell (`skysh`) just run:
+```
+skysh -C /path/to/cert.pem --port [SSLPORT]
+```
+and you'll be on a secure connection. Don't forget the SSL port! The skytable daemon binds the secure
+listener on a different port when in multi-socket mode.
+:::