blitzwing/cryptpad
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix comments in nginx file

Browse source
This commit is contained in:
yflory 2023-10-03 12:04:55 +02:00
parent 1c2764dbb8
commit 6c6220edfc
1 changed files with 3 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
docs/example.nginx.conf
View file

@ -12,35 +12,14 @@ server {
include letsencrypt-webroot; include letsencrypt-webroot;
# CryptPad serves static assets over these two domains. # CryptPad serves static assets over these two domains.
# `main_domain` is what users will enter in their address bar. # `your-main-domain` is what users will enter in their address bar.
# Privileged computation such as key management is handled in this scope # Privileged computation such as key management is handled in this scope
# UI content is loaded via the `sandbox_domain`. # UI content is loaded via the `your-sandbox-domain`.
# "Content Security Policy" headers prevent content loaded via the sandbox # "Content Security Policy" headers prevent content loaded via the sandbox
# from accessing privileged information. # from accessing privileged information.
# These variables must be different to take advantage of CryptPad's sandboxing techniques. # This setup allows to take advantage of CryptPad's sandboxing techniques.
# In the event of an XSS vulnerability in CryptPad's front-end code # In the event of an XSS vulnerability in CryptPad's front-end code
# this will limit the amount of information accessible to attackers. # this will limit the amount of information accessible to attackers.
set $main_domain "your-main-domain.com";
set $sandbox_domain "your-sandbox-domain.com";
# By default CryptPad forbids remote domains from embedding CryptPad documents in iframes.
# The sandbox domain must always be permitted in order for the platform to function.
# If you wish to enable remote embedding you may change the value below to "*"
# as per the commented value.
set $allowed_origins "https://${sandbox_domain}";
#set $allowed_origins "*";
# CryptPad's dynamic content (websocket traffic and encrypted blobs)
# can be served over separate domains. Using dedicated domains (or subdomains)
# for these purposes allows you to move them to a separate machine at a later date
# if you find that a single machine cannot handle all of your users.
# If you don't use dedicated domains, this can be the same as $main_domain
# If you do, they can be added as exceptions to any rules which block connections to remote domains.
# You can find these variables referenced below in the relevant places
set $api_domain "api.your-main-domain.com";
set $files_domain "files.your-main-domain.com";
# nginx doesn't let you set server_name via variables, so you need to hardcode your domains here
server_name your-main-domain.com your-sandbox-domain.com; server_name your-main-domain.com your-sandbox-domain.com;
# You'll need to Set the path to your certificates and keys here # You'll need to Set the path to your certificates and keys here