1
0
Fork 0
peertube/support/doc/production.md

328 lines
8.9 KiB
Markdown
Raw Normal View History

2018-01-12 12:07:41 -05:00
# Production guide
2018-01-29 05:23:38 -05:00
* [Installation](#installation)
* [Upgrade](#upgrade)
2018-01-29 05:23:38 -05:00
2018-01-12 12:07:41 -05:00
## Installation
2018-07-24 10:22:21 -04:00
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://github.com/Chocobozzz/PeerTube/blob/develop/FAQ.md#should-i-have-a-big-server-to-run-peertube).
2018-02-09 07:38:19 -05:00
2018-01-12 12:07:41 -05:00
### Dependencies
**Follow the steps of the [dependencies guide](dependencies.md).**
2018-01-12 12:07:41 -05:00
### PeerTube user
Create a `peertube` user with `/var/www/peertube` home:
2018-01-12 12:07:41 -05:00
2018-01-12 12:55:45 -05:00
```
$ sudo useradd -m -d /var/www/peertube -s /bin/bash -p peertube peertube
```
Set its password:
```
$ sudo passwd peertube
2018-01-12 12:07:41 -05:00
```
**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.
2018-01-12 12:07:41 -05:00
### Database
Create the production database and a peertube user inside PostgreSQL:
2018-01-12 12:07:41 -05:00
2018-01-12 12:55:45 -05:00
```
$ sudo -u postgres createuser -P peertube
$ sudo -u postgres createdb -O peertube peertube_prod
2018-01-12 12:07:41 -05:00
```
2018-07-19 10:17:54 -04:00
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
2018-01-12 12:07:41 -05:00
Fetch the latest tagged version of Peertube
```
$ VERSION=$(curl -s https://api.github.com/repos/chocobozzz/peertube/releases/latest | grep tag_name | cut -d '"' -f 4) && echo "Latest Peertube version is $VERSION"
```
Open the peertube directory, create a few required directories
```
$ cd /var/www/peertube && sudo -u peertube mkdir config storage versions && cd versions
```
Download the latest version of the Peertube client, unzip it and remove the zip
2018-01-12 12:55:45 -05:00
```
$ 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
```
2018-05-26 21:25:10 -04:00
Install Peertube:
```
$ cd ../ && sudo -u peertube ln -s versions/peertube-${VERSION} ./peertube-latest
$ cd ./peertube-latest && sudo -H -u peertube yarn install --production --pure-lockfile
2018-01-12 12:07:41 -05:00
```
### PeerTube configuration
Copy example configuration:
2018-01-12 12:55:45 -05:00
```
$ cd /var/www/peertube && sudo -u peertube cp peertube-latest/config/production.yaml.example config/production.yaml
2018-01-12 12:07:41 -05:00
```
Then edit the `config/production.yaml` file according to your webserver
configuration.
2018-01-12 12:07:41 -05:00
**PeerTube does not support webserver host change**. Keep in mind your domain name is definitive after your first PeerTube start.
2018-01-12 12:07:41 -05:00
### Webserver
We only provide official configuration files for Nginx.
2018-01-12 12:07:41 -05:00
Copy the nginx configuration template:
2018-01-12 12:55:45 -05:00
```
$ sudo cp /var/www/peertube/peertube-latest/support/nginx/peertube /etc/nginx/sites-available/peertube
2018-01-12 12:07:41 -05:00
```
2018-01-18 11:44:13 -05:00
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).
2018-01-12 12:07:41 -05:00
2018-01-12 12:55:45 -05:00
```
2018-01-12 12:07:41 -05:00
$ sudo vim /etc/nginx/sites-available/peertube
```
2018-02-16 05:04:12 -05:00
Activate the configuration file:
```
$ sudo ln -s /etc/nginx/sites-available/peertube /etc/nginx/sites-enabled/peertube
```
To generate the certificate for your domain as required to make https work you can use [Let's Encrypt](https://letsencrypt.org/):
```
$ sudo systemctl stop nginx
2018-03-01 10:12:00 -05:00
$ sudo vim /etc/nginx/sites-available/peertube # Comment ssl_certificate and ssl_certificate_key lines
2018-02-16 05:04:12 -05:00
$ sudo certbot --authenticator standalone --installer nginx --post-hook "systemctl start nginx"
2018-03-01 10:12:00 -05:00
$ sudo vim /etc/nginx/sites-available/peertube # Uncomment ssl_certificate and ssl_certificate_key lines
$ sudo systemctl reload nginx
```
Remember your certificate will expire in 90 days, and thus needs renewal.
2018-01-12 12:07:41 -05:00
2018-02-16 05:04:12 -05:00
Now you have the certificates you can reload nginx:
2018-01-12 12:07:41 -05:00
2018-01-12 12:55:45 -05:00
```
2018-01-12 12:07:41 -05:00
$ sudo systemctl reload nginx
```
**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.
2018-03-20 03:28:20 -04:00
### systemd
2018-01-12 12:07:41 -05:00
2018-03-20 03:28:20 -04:00
If your OS uses systemd, copy the configuration template:
2018-01-12 12:07:41 -05:00
2018-01-12 12:55:45 -05:00
```
$ sudo cp /var/www/peertube/peertube-latest/support/systemd/peertube.service /etc/systemd/system/
2018-01-12 12:07:41 -05:00
```
Update the service file:
2018-01-12 12:55:45 -05:00
```
$ sudo vim /etc/systemd/system/peertube.service
2018-01-12 12:07:41 -05:00
```
Tell systemd to reload its config:
2018-01-12 12:55:45 -05:00
```
$ sudo systemctl daemon-reload
2018-01-12 12:07:41 -05:00
```
2018-01-15 05:10:46 -05:00
If you want to start PeerTube on boot:
```
2018-01-17 05:47:45 -05:00
$ sudo systemctl enable peertube
2018-01-15 05:10:46 -05:00
```
2018-03-20 03:28:20 -04:00
Run:
2018-01-12 12:07:41 -05:00
2018-01-12 12:55:45 -05:00
```
$ sudo systemctl start peertube
$ sudo journalctl -feu peertube
2018-01-12 12:07:41 -05:00
```
2018-08-21 04:48:57 -04:00
**FreeBSD**
On FreeBSD, copy the startup script and update rc.conf:
2018-03-19 17:48:15 -04:00
```
$ sudo install -m 0555 /var/www/peertube/peertube-latest/support/freebsd/peertube /usr/local/etc/rc.d/
$ sudo sysrc peertube_enable="YES"
2018-03-19 17:48:15 -04:00
```
2018-03-20 03:28:20 -04:00
Run:
2018-03-19 17:48:15 -04:00
```
$ sudo service peertube start
```
2018-01-12 12:07:41 -05:00
### Administrator
The administrator password is automatically generated and can be found in the
logs. You can set another password with:
2018-01-12 12:55:45 -05:00
```
$ cd /var/www/peertube/peertube-latest && NODE_CONFIG_DIR=/var/www/peertube/config NODE_ENV=production npm run reset-password -- -u root
2018-01-12 12:07:41 -05:00
```
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/
* Check [available CLI tools](/support/doc/tools.md)
2018-03-15 09:31:08 -04:00
2018-01-12 12:07:41 -05:00
## Upgrade
2018-07-19 10:17:54 -04:00
### PeerTube instance
**Check the changelog (in particular BREAKING CHANGES!):** https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md
2018-02-14 05:09:02 -05:00
#### Auto (minor versions only)
2018-03-29 08:27:55 -04:00
The password it asks is PeerTube's database user password.
```
$ cd /var/www/peertube/peertube-latest/scripts && sudo -H -u peertube ./upgrade.sh
```
2018-02-14 05:09:02 -05:00
#### Manually
2018-01-26 04:50:05 -05:00
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 -u postgres pg_dump -F c peertube_prod | sudo -u peertube tee "$SQL_BACKUP_PATH" >/dev/null
```
2018-01-26 04:50:05 -05:00
Fetch the latest tagged version of Peertube:
2018-01-19 07:58:13 -05:00
```
2018-01-26 04:50:05 -05:00
$ VERSION=$(curl -s https://api.github.com/repos/chocobozzz/peertube/releases/latest | grep tag_name | cut -d '"' -f 4) && echo "Latest Peertube version is $VERSION"
2018-01-19 07:58:13 -05:00
```
2018-01-26 04:50:05 -05:00
Download the new version and unzip it:
2018-01-12 12:55:45 -05:00
```
2018-01-26 04:50:05 -05:00
$ cd /var/www/peertube/versions && \
sudo -u peertube wget -q "https://github.com/Chocobozzz/PeerTube/releases/download/${VERSION}/peertube-${VERSION}.zip" && \
2018-01-26 04:50:05 -05:00
sudo -u peertube unzip -o peertube-${VERSION}.zip && \
sudo -u peertube rm peertube-${VERSION}.zip
```
2018-01-29 05:58:07 -05:00
Install node dependencies:
2018-01-26 04:50:05 -05:00
```
2018-01-29 05:58:07 -05:00
$ cd /var/www/peertube/versions/peertube-${VERSION} && \
sudo -H -u peertube yarn install --production --pure-lockfile
2018-01-26 04:50:05 -05:00
```
2018-01-29 05:58:07 -05:00
Copy new configuration defaults values and update your configuration file:
2018-01-26 04:50:05 -05:00
2018-01-12 12:07:41 -05:00
```
2018-01-29 05:58:07 -05:00
$ sudo -u peertube cp /var/www/peertube/versions/peertube-${VERSION}/config/default.yaml /var/www/peertube/config/default.yaml
2018-02-14 05:09:02 -05:00
$ diff /var/www/peertube/versions/peertube-${VERSION}/config/production.yaml.example /var/www/peertube/config/production.yaml
2018-01-26 04:50:05 -05:00
```
2018-01-29 05:58:07 -05:00
Change the link to point to the latest version:
2018-01-26 04:50:05 -05:00
```
2018-01-29 05:58:07 -05:00
$ cd /var/www/peertube && \
sudo unlink ./peertube-latest && \
2018-01-29 05:58:07 -05:00
sudo -u peertube ln -s versions/peertube-${VERSION} ./peertube-latest
2018-01-26 04:50:05 -05:00
```
### 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:
```
$ sudo systemctl reload nginx
```
If you changed your systemd configuration:
2018-01-29 05:58:07 -05:00
2018-01-26 04:50:05 -05:00
```
$ sudo systemctl daemon-reload
```
Restart PeerTube and check the logs:
```
$ sudo systemctl restart peertube && sudo journalctl -fu peertube
2018-01-26 04:50:05 -05:00
```
### Things went wrong?
2018-01-26 04:50:05 -05:00
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 && sudo -u peertube unlink ./peertube-latest && \
sudo -u peertube ln -s "versions/peertube-$OLD_VERSION" peertube-latest && \
sudo -u postgres pg_restore -c -C -d postgres "$SQL_BACKUP_PATH" && \
sudo systemctl restart peertube
```