Added section related to https deployment #556 #557
Conversation
fernandinand
requested review from
PeterPetrik
and removed request for
PeterPetrik
There was a problem hiding this comment.
I think do not mention docker-compose here. As we discussed with @varmar05 , ssl-proxy.conf is just example of how to use it with nginx. You can follow this guide on your infrastructure. If you want to use it with docker-compose as you mentioned, ssl-proxy.conf should be updated also with specific paths from nginx.conf (/download , etc.)
I think that you can mention here also specific security headers from ssl-proxy.conf.
src/server/security/index.md
Outdated
|
|
||
| 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 <GitHubRepo id="MerginMaps/server/blob/master/docker-compose.yml" desc="proxy service section" /> |
There was a problem hiding this comment.
I think we do not need to menion this CE docker-compose. Use just your docker-compose or something like this.
| @@ -249,6 +253,7 @@ shapefiles | |||
| spatialindex | |||
| spatialite | |||
| sqlite | |||
| ssl | |||
src/server/security/index.md
Outdated
| - ./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/ |
There was a problem hiding this comment.
I am not sure If we want to discuss here also logs. There is no context for it.
src/server/security/index.md
Outdated
| # Secure Mergin Maps installation | ||
|
|
||
| ::: warning | ||
| This sections aims to provide some guidelines and a minimalistic example on how to secure a Mergin Maps deployment. |
There was a problem hiding this comment.
| This sections aims to provide some guidelines and a minimalistic example on how to secure a Mergin Maps deployment. | |
| This sections aims to provide some guidelines and a minimalistic example on how to secure a <MainPlatformName /> deployment. |
Please review this new section related to HTTPS deployment