X-Git-Url: https://git.immae.eu/?a=blobdiff_plain;f=support%2Fdoc%2Fproduction.md;h=4a8c488ee033f625fd8ab9e6bcd2354c43a3293a;hb=ef62d58674a23ecee2dafef3b42e2bb771c9e6f6;hp=3d1be6b45fa1d8f57af53c63cbea053f541e4f8a;hpb=65fcf1e9c28cd801c3c7b0c70f28d1ed52d3fd3a;p=github%2FChocobozzz%2FPeerTube.git diff --git a/support/doc/production.md b/support/doc/production.md index 3d1be6b45..4a8c488ee 100644 --- a/support/doc/production.md +++ b/support/doc/production.md @@ -39,7 +39,7 @@ Create the production database and a peertube user inside PostgreSQL: ``` $ sudo -u postgres createuser -P peertube -$ sudo -u postgres createdb -O peertube peertube_prod +$ sudo -u postgres createdb -O peertube -E UTF8 -T template0 peertube_prod ``` Then enable extensions PeerTube needs: @@ -96,6 +96,14 @@ 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. + +``` +$ sudo sed -i 's/${WEBSERVER_HOST}/[peertube-domain]/g' /etc/nginx/sites-available/peertube +$ sudo sed -i 's/${PEERTUBE_HOST}/localhost:9000/g' /etc/nginx/sites-available/peertube +``` + Then modify the webserver configuration file. Please pay attention to the `alias` keys of the static locations. It should correspond to the paths of your storage directories (set in the configuration file inside the `storage` key). @@ -113,9 +121,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 ``` @@ -134,6 +140,21 @@ On FreeBSD you can use [Dehydrated](https://dehydrated.io/) `security/dehydrated $ sudo pkg install dehydrated ``` +### TCP/IP Tuning + +A lot of your instance's raw performance is dependent on a properly tuned machine and more specifically, reverse-proxy. We provide support for Nginx and spent a lot of time putting sane defaults in it, but we strongly advise you to follow up with instructions in https://github.com/denji/nginx-tuning as needed. + +**On Linux** + +``` +$ sudo cp /var/www/peertube/peertube-latest/support/sysctl.d/30-peertube-tcp.conf /etc/sysctl.d/ +$ sudo sysctl -p /etc/sysctl.d/30-peertube-tcp.conf +``` + +Your distro may enable this by default, but at least Debian 9 does not, and the default FIFO +scheduler is quite prone to "Buffer Bloat" and extreme latency when dealing with slower client +links as we often encounter in a video server. + ### systemd If your OS uses systemd, copy the configuration template: @@ -142,7 +163,7 @@ If your OS uses systemd, copy the configuration template: $ sudo cp /var/www/peertube/peertube-latest/support/systemd/peertube.service /etc/systemd/system/ ``` -Update the service file: +Check the service file (PeerTube paths and security directives): ``` $ sudo vim /etc/systemd/system/peertube.service @@ -172,9 +193,8 @@ $ sudo journalctl -feu peertube On FreeBSD, copy the startup script and update rc.conf: ``` -$ sudo cp /var/www/peertube/peertube-latest/support/freebsd/peertube /usr/local/etc/rc.d/ -$ sudo chmod +x /usr/local/etc/rc.d/peertube -$ sudo echo peertube_enable="YES" >> /etc/rc.conf +$ sudo install -m 0555 /var/www/peertube/peertube-latest/support/freebsd/peertube /usr/local/etc/rc.d/ +$ sudo sysrc peertube_enable="YES" ``` Run: @@ -183,6 +203,27 @@ Run: $ sudo service peertube start ``` +### OpenRC + +If your OS uses OpenRC, copy the service script: + +``` +$ sudo cp /var/www/peertube/peertube-latest/support/init.d/peertube /etc/init.d/ +``` + +If you want to start PeerTube on boot: + +``` +$ sudo rc-update add peertube default +``` + +Run and print last logs: + +``` +$ sudo /etc/init.d/peertube start +$ tail -f /var/log/peertube/peertube.log +``` + ### Administrator The administrator password is automatically generated and can be found in the @@ -192,12 +233,16 @@ logs. You can set another password with: $ cd /var/www/peertube/peertube-latest && NODE_CONFIG_DIR=/var/www/peertube/config NODE_ENV=production npm run reset-password -- -u root ``` +Alternatively you can set the environment variable `PT_INITIAL_ROOT_PASSWORD`, +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/ + * Add your instance to the public PeerTube instances index if you want to: https://instances.joinpeertube.org/ + * Check [available CLI tools](/support/doc/tools.md) ## Upgrade