Fill documentation with required secret conf
This commit is contained in:
parent
a3e5f804ad
commit
1ea868a945
|
@ -12,6 +12,7 @@ webserver:
|
|||
|
||||
# Secrets you need to generate the first time you run PeerTube
|
||||
secrets:
|
||||
# Generate one using `openssl rand -hex 32`
|
||||
peertube: ''
|
||||
|
||||
rates_limit:
|
||||
|
|
|
@ -10,6 +10,7 @@ webserver:
|
|||
|
||||
# Secrets you need to generate the first time you run PeerTube
|
||||
secret:
|
||||
# Generate one using `openssl rand -hex 32`
|
||||
peertube: ''
|
||||
|
||||
rates_limit:
|
||||
|
|
|
@ -49,6 +49,7 @@ In the downloaded example [.env](https://github.com/Chocobozzz/PeerTube/blob/mas
|
|||
- `<MY POSTGRES PASSWORD>`
|
||||
- `<MY DOMAIN>` without 'https://'
|
||||
- `<MY EMAIL ADDRESS>`
|
||||
- `<MY PEERTUBE SECRET>`
|
||||
|
||||
Other environment variables are used in
|
||||
[/support/docker/production/config/custom-environment-variables.yaml](https://github.com/Chocobozzz/PeerTube/blob/master/support/docker/production/config/custom-environment-variables.yaml) and can be
|
||||
|
|
|
@ -115,8 +115,14 @@ $ 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
|
||||
and database configuration (`webserver`, `database`, `redis`, `smtp` and `admin.email` sections in particular).
|
||||
Then edit the `config/production.yaml` file according to your webserver and database configuration. In particular:
|
||||
* `webserver`: Reverse proxy public information
|
||||
* `secrets`: Secret strings you must generate manually (PeerTube version >= 5.0)
|
||||
* `database`: PostgreSQL settings
|
||||
* `redis`: Redis settings
|
||||
* `smtp`: If you want to use emails
|
||||
* `admin.email`: To correctly fill `root` user email
|
||||
|
||||
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.
|
||||
|
|
|
@ -22,6 +22,9 @@ PEERTUBE_WEBSERVER_HOSTNAME=<MY DOMAIN>
|
|||
# pass them as a comma separated array:
|
||||
PEERTUBE_TRUST_PROXY=["127.0.0.1", "loopback", "172.18.0.0/16"]
|
||||
|
||||
# Generate one using `openssl rand -hex 32`
|
||||
PEERTUBE_SECRET=<MY PEERTUBE SECRET>
|
||||
|
||||
# E-mail configuration
|
||||
# If you use a Custom SMTP server
|
||||
#PEERTUBE_SMTP_USERNAME=
|
||||
|
|
|
@ -7,6 +7,9 @@ webserver:
|
|||
__name: "PEERTUBE_WEBSERVER_HTTPS"
|
||||
__format: "json"
|
||||
|
||||
secrets:
|
||||
peertube: "PEERTUBE_SECRET"
|
||||
|
||||
trust_proxy:
|
||||
__name: "PEERTUBE_TRUST_PROXY"
|
||||
__format: "json"
|
||||
|
|
Loading…
Reference in New Issue