forks/peertube
1
0
Fork 0
Code Releases Activity

Fix certbot section

Browse source
This commit is contained in:
Chocobozzz 2020-08-14 14:59:15 +02:00
parent 5a6de09313
commit 2c92b0634f
No known key found for this signature in database
GPG key ID: 583A612D890159BE
1 changed files with 4 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
support/doc/production.md
View file

@ -96,8 +96,8 @@ Copy the nginx configuration template:
$ sudo cp /var/www/peertube/peertube-latest/support/nginx/peertube /etc/nginx/sites-available/peertube
```
Then set the domain for the webserver configuration file.
Replace `[peertube-domain]` with the domain for the peertube server.
Then set the domain for the webserver configuration file.
Replace `[peertube-domain]` with the domain for the peertube server.
```
$ sudo sed -i 's/peertube.example.com/[peertube-domain]/g' /etc/nginx/sites-available/peertube
@ -120,9 +120,7 @@ To generate the certificate for your domain as required to make https work you c
```
$ sudo systemctl stop nginx
$ sudo vim /etc/nginx/sites-available/peertube # Comment ssl_certificate and ssl_certificate_key lines
$ sudo certbot --authenticator standalone --installer nginx --post-hook "systemctl start nginx"
$ sudo vim /etc/nginx/sites-available/peertube # Uncomment ssl_certificate and ssl_certificate_key lines
$ sudo certbot certonly --standalone --post-hook "systemctl start nginx"
$ sudo systemctl reload nginx
```
@ -238,7 +236,7 @@ to your own administrator password, although it must be 6 characters or more.
### What now?
Now your instance is up you can:
* Subscribe to the mailing list for PeerTube administrators: https://framalistes.org/sympa/subscribe/peertube-admin
* Add you instance to the public PeerTube instances index if you want to: https://instances.peertu.be/
* Check [available CLI tools](/support/doc/tools.md)