X-Git-Url: https://git.immae.eu/?a=blobdiff_plain;f=support%2Fdoc%2Fproduction.md;h=81748ae166e86c2756fdb18c4692da4a228fdd13;hb=6a3391bcede8e7a2bec83963221c112e6752b1a8;hp=9241ab61512dd147b88c8e113f1b26f27ba066c2;hpb=a640b861b985413992867a7d9b68a1e3ba7fe570;p=github%2FChocobozzz%2FPeerTube.git diff --git a/support/doc/production.md b/support/doc/production.md index 9241ab615..81748ae16 100644 --- a/support/doc/production.md +++ b/support/doc/production.md @@ -1,15 +1,16 @@ # Production guide * [Installation](#installation) - * [Upgrade](#upgrade) + * [Upgrade](#upgrade) ## Installation -**Please don't install PeerTube for production on a small device behind a low bandwidth connection because it could slow down the fediverse.** +Please don't install PeerTube for production on a device behind a low bandwidth connection (example: your ADSL link). +If you want information about the appropriate hardware to run PeerTube, please see the [FAQ](https://joinpeertube.org/en_US/faq#should-i-have-a-big-server-to-run-peertube). ### Dependencies -Follow the steps of the [dependencies guide](dependencies.md). +**Follow the steps of the [dependencies guide](dependencies.md).** ### PeerTube user @@ -24,13 +25,35 @@ Set its password: $ sudo passwd peertube ``` +**On FreeBSD** + +``` +$ sudo pw useradd -n peertube -d /var/www/peertube -s /usr/local/bin/bash -m +$ sudo passwd peertube +``` +or use `adduser` to create it interactively. + ### Database Create the production database and a peertube user inside PostgreSQL: ``` +$ cd /var/www/peertube $ sudo -u postgres createuser -P peertube -$ sudo -u postgres createdb -O peertube peertube_prod +``` + +Here you should enter a password for PostgreSQL `peertube` user, that should be copied in `production.yaml` file. +Don't just hit enter else it will be empty. + +``` +$ sudo -u postgres createdb -O peertube -E UTF8 -T template0 peertube_prod +``` + +Then enable extensions PeerTube needs: + +``` +$ sudo -u postgres psql -c "CREATE EXTENSION pg_trgm;" peertube_prod +$ sudo -u postgres psql -c "CREATE EXTENSION unaccent;" peertube_prod ``` ### Prepare PeerTube directory @@ -42,31 +65,47 @@ $ VERSION=$(curl -s https://api.github.com/repos/chocobozzz/peertube/releases/la Open the peertube directory, create a few required directories ``` -$ cd /var/www/peertube && sudo -u peertube mkdir config storage versions && cd versions +$ cd /var/www/peertube +$ sudo -u peertube mkdir config storage versions +$ sudo -u peertube chmod 750 config/ ``` Download the latest version of the Peertube client, unzip it and remove the zip ``` +$ cd /var/www/peertube/versions $ sudo -u peertube wget -q "https://github.com/Chocobozzz/PeerTube/releases/download/${VERSION}/peertube-${VERSION}.zip" -$ sudo -u peertube unzip peertube-${VERSION}.zip && sudo -u peertube rm peertube-${VERSION}.zip +$ sudo -u peertube unzip -q peertube-${VERSION}.zip && sudo -u peertube rm peertube-${VERSION}.zip ``` -Install Peertube +Install Peertube: ``` -$ cd ../ && sudo -u peertube ln -s versions/peertube-${VERSION} ./peertube-latest +$ cd /var/www/peertube +$ sudo -u peertube ln -s versions/peertube-${VERSION} ./peertube-latest $ cd ./peertube-latest && sudo -H -u peertube yarn install --production --pure-lockfile ``` ### PeerTube configuration -Copy example configuration: +Copy the default configuration file that contains the default configuration provided by PeerTube. +You **must not** update this file. + +``` +$ cd /var/www/peertube +$ sudo -u peertube cp peertube-latest/config/default.yaml config/default.yaml +``` + +Now copy the production example configuration: ``` -$ cd /var/www/peertube && sudo -u peertube cp peertube-latest/config/production.yaml.example config/production.yaml +$ cd /var/www/peertube +$ sudo -u peertube cp peertube-latest/config/production.yaml.example config/production.yaml ``` Then edit the `config/production.yaml` file according to your webserver -configuration. +and database configuration (`webserver`, `database`, `redis`, `smtp` and `admin.email` sections in particular). +Keys defined in `config/production.yaml` will override keys defined in `config/default.yaml`. + +**PeerTube does not support webserver host change**. Even though [PeerTube CLI can help you to switch hostname](https://docs.joinpeertube.org/maintain-tools?id=update-hostjs) there's no official support for that since it is a risky operation that might result in unforeseen errors. ### Webserver @@ -78,6 +117,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}/127.0.0.1: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). @@ -95,26 +142,54 @@ To generate the certificate for your domain as required to make https work you c ``` $ sudo systemctl stop nginx -$ sudo certbot --authenticator standalone --installer nginx --post-hook "systemctl start nginx" +$ sudo certbot certonly --standalone --post-hook "systemctl restart nginx" +$ sudo systemctl reload nginx ``` -Remember your certificate will expire in 90 days, and thus needs renewal. - Now you have the certificates you can reload nginx: ``` $ sudo systemctl reload nginx ``` -### Systemd +Certbot should have installed a cron to automatically renew your certificate. +Since our nginx template supports webroot renewal, we suggest you to update the renewal config file to use the `webroot` authenticator: + +``` +$ # Replace authenticator = standalone by authenticator = webroot +$ # Add webroot_path = /var/www/certbot +$ sudo vim /etc/letsencrypt/renewal/your-domain.com.conf +``` + +**FreeBSD** +On FreeBSD you can use [Dehydrated](https://dehydrated.io/) `security/dehydrated` for [Let's Encrypt](https://letsencrypt.org/) + +``` +$ sudo pkg install dehydrated +``` + +### TCP/IP Tuning + +**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. -Copy the SystemD configuration template: +### systemd + +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 @@ -133,29 +208,79 @@ If you want to start PeerTube on boot: $ sudo systemctl enable peertube ``` -### Run +Run: ``` $ sudo systemctl start peertube $ sudo journalctl -feu peertube ``` +**FreeBSD** +On FreeBSD, copy the startup script and update 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: + +``` +$ 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 -logs. You can set another password with: +The administrator password is automatically generated and can be found in the PeerTube +logs (path defined in `production.yaml`). You can also 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: + + * 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 -#### Auto (minor versions only) +### PeerTube instance + +**Check the changelog (in particular BREAKING CHANGES!):** https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md + +#### Auto + +The password it asks is PeerTube's database user password. ``` -$ cd /var/www/peertube/peertube-latest/scripts && sudo -u peertube ./upgrade.sh -$ sudo systemctl restart peertube && sudo journalctl -fu peertube +$ cd /var/www/peertube/peertube-latest/scripts && sudo -H -u peertube ./upgrade.sh ``` #### Manually @@ -165,7 +290,7 @@ Make a SQL backup ``` $ SQL_BACKUP_PATH="backup/sql-peertube_prod-$(date -Im).bak" && \ cd /var/www/peertube && sudo -u peertube mkdir -p backup && \ - sudo pg_dump -U peertube -W -h localhost -F c peertube_prod -f "$SQL_BACKUP_PATH" + sudo -u postgres pg_dump -F c peertube_prod | sudo -u peertube tee "$SQL_BACKUP_PATH" >/dev/null ``` Fetch the latest tagged version of Peertube: @@ -187,7 +312,7 @@ Install node dependencies: ``` $ cd /var/www/peertube/versions/peertube-${VERSION} && \ - sudo -u peertube yarn install --production --pure-lockfile + sudo -H -u peertube yarn install --production --pure-lockfile ``` Copy new configuration defaults values and update your configuration file: @@ -205,20 +330,52 @@ $ cd /var/www/peertube && \ sudo -u peertube ln -s versions/peertube-${VERSION} ./peertube-latest ``` +### nginx + +Check changes in nginx configuration: + +``` +$ cd /var/www/peertube/versions +$ diff "$(ls --sort=t | head -2 | tail -1)/support/nginx/peertube" "$(ls --sort=t | head -1)/support/nginx/peertube" +``` + +### systemd + +Check changes in systemd configuration: + +``` +$ cd /var/www/peertube/versions +$ diff "$(ls --sort=t | head -2 | tail -1)/support/systemd/peertube.service" "$(ls --sort=t | head -1)/support/systemd/peertube.service" +``` + +### Restart PeerTube + +If you changed your nginx configuration: -Restart PeerTube: ``` -$ sudo systemctl restart peertube +$ sudo systemctl reload nginx +``` + +If you changed your systemd configuration: + +``` +$ sudo systemctl daemon-reload +``` + +Restart PeerTube and check the logs: + +``` +$ sudo systemctl restart peertube && sudo journalctl -fu peertube ``` -### Things went wrong? +### Things went wrong? Change `peertube-latest` destination to the previous version and restore your SQL backup: ``` $ OLD_VERSION="v0.42.42" && SQL_BACKUP_PATH="backup/sql-peertube_prod-2018-01-19T10:18+01:00.bak" && \ - cd /var/www/peertube && unlink ./peertube-latest && \ + cd /var/www/peertube && sudo -u peertube unlink ./peertube-latest && \ sudo -u peertube ln -s "versions/peertube-$OLD_VERSION" peertube-latest && \ - pg_restore -U peertube -W -h localhost -c -d peertube_prod "$SQL_BACKUP_PATH" + sudo -u postgres pg_restore -c -C -d postgres "$SQL_BACKUP_PATH" && \ sudo systemctl restart peertube ```