Added section related to https deployment #556

Author: fernandinand

Diff for: src/.vuepress/sidebar/en.js

@@ -125,6 +125,7 @@ module.exports = {
             children: [
                 '/server/',
                 '/server/install/',
+                '/server/security/',
                 '/server/upgrade/',
                 '/server/administer/',
                 '/server/troubleshoot/',

Diff for: src/index.md

@@ -105,6 +105,7 @@ The ecosystem consist of various components:
 ## Custom Server
 - [Overview](./server/)
 - [Install](./server/install/)
+- [Security](./server/security/)
 - [Upgrade](./server/upgrade/)
 - [Administer](./server/administer/)
 - [Troubleshoot Custom Servers](./server/troubleshoot/)

Diff for: src/server/security/index.md

@@ -0,0 +1,44 @@
+# Secure Mergin Maps installation
+
+For security and privacy reasons Mergin Maps deployments should enable HTTPS secured connection via certificate file.
+
+We provide a template configuration file [ssl-proxy.conf](https://github.com/MerginMaps/server/blob/master/ssl-proxy.conf) as base for your costumization.
+
+Let's have a quick look at the main sections:
+
+``` shell
+    server {
+        listen              443 ssl;
+        server_name         merginmaps.company.com; # FIXME
+        client_max_body_size 4G;
+        
+        ...
+```
+
+Here we enable SSL via the defaul `443` port and configure name-based HTTPS server via `server_name`. Here you should change this according to your target server name.
+
+We don't recommend setting a `client_max_body_size` higher than specified, because that might lead to timeouts while uploading your data to Mergin Maps.
+
+Next, you need to point your certificate files to NGINX configuration. This is done on the next lines on the secured configuration:
+
+``` shell
+    ...
+    ssl_certificate_key /etc/letsencrypt/live/merginmaps.company.com/privkey.pem; # FIXME
+    ssl_certificate     /etc/letsencrypt/live/merginmaps.company.com/fullchain.pem; # FIXME
+    ...
+```
+
+The above example uses automated keys generated by Certbot. For more information, visit [CertBot](https://certbot.eff.org/instructions) website and check how you can generate your own keys.
+
+Lastly, adjust the provided nginx `docker compose` deployment file, on the following [section](https://github.com/MerginMaps/server/blob/master/docker-compose.yml#L95):
+
+``` shell
+       - "8080:8080"
+     volumes:
+       - ./projects:/data  # map data dir to host
+-      - ./nginx.conf:/etc/nginx/conf.d/default.conf
++      - ./ssl-proxy.conf:/etc/nginx/conf.d/default.conf
+       - ./logs:/var/log/nginx/
+     networks:
+       - merginmaps
+```