logo

pleroma

My custom branche(s) on git.pleroma.social/pleroma/pleroma
commit: b4b314be5d885d7190f9ea4edacac2a2c14e2eca
parent: 9e6ae447294d055af6add2efa9aca0024a252fe1
Author: lambda <pleromagit@rogerbraun.net>
Date:   Sat, 21 Apr 2018 07:59:49 +0000

Merge branch 'nginx-certbot-doc' into 'develop'

Add info about certbot with the webroot plugin to pleroma.nginx

See merge request pleroma/pleroma!125

Diffstat:

Minstallation/pleroma.nginx11++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/installation/pleroma.nginx b/installation/pleroma.nginx @@ -4,7 +4,7 @@ # 1. Install your TLS certificate, possibly using Let's Encrypt. # 2. Replace 'example.tld' with your instance's domain wherever it appears. # 3. Copy this file to /etc/nginx/sites-available/ and then add a symlink to it -# in /etc/nginx/sites-enabled/ and restart nginx. +# in /etc/nginx/sites-enabled/ and run 'nginx -s reload' or restart nginx. proxy_cache_path /tmp/pleroma-media-cache levels=1:2 keys_zone=pleroma_media_cache:10m max_size=10g inactive=720m use_temp_path=off; @@ -13,6 +13,15 @@ server { listen 80; server_name example.tld; return 301 https://$server_name$request_uri; + + # Uncomment this if you need to use the 'webroot' method with certbot. Make sure + # that you also create the .well-known/acme-challenge directory structure in pleroma/priv/static and + # that is is accessible by the webserver. You may need to load this file with the ssl + # server block commented out, run certbot to get the certificate, and then uncomment it. + # + # location ~ /\.well-known/acme-challenge { + # root <path to install>/pleroma/priv/static/; + # } } server {