Fix docker compose guide

pull/5817/head
Chocobozzz 2023-05-16 10:38:04 +02:00
parent cc518fdbcb
commit 77666e3433
No known key found for this signature in database
GPG Key ID: 583A612D890159BE
1 changed files with 8 additions and 7 deletions

View File

@ -64,7 +64,8 @@ intuited from usage.
#### Webserver #### Webserver
::: info ::: info
The docker compose file includes a configured web server. You can skip this part and comment the appropriate section in the docker compose if you use another webserver/proxy.::: The docker compose file includes a configured web server. You can skip this part and comment the appropriate section in the docker compose if you use another webserver/proxy.
:::
Install the template that the nginx container will use. Install the template that the nginx container will use.
The container will generate the configuration by replacing `${WEBSERVER_HOST}` and `${PEERTUBE_HOST}` using your docker compose env file. The container will generate the configuration by replacing `${WEBSERVER_HOST}` and `${PEERTUBE_HOST}` using your docker compose env file.
@ -91,20 +92,20 @@ _note_: Newer versions of compose are called with `docker compose` instead of `d
Run your containers: Run your containers:
```shell ```shell
docker-compose up docker compose up
``` ```
#### Obtaining your automatically-generated admin credentials #### Obtaining your automatically-generated admin credentials
You can change the automatically created password for user root by running this command from peertube's root directory: You can change the automatically created password for user root by running this command from peertube's root directory:
```shell ```shell
docker-compose exec -u peertube peertube npm run reset-password -- -u root docker compose exec -u peertube peertube npm run reset-password -- -u root
``` ```
You can also grep your peertube container's logs for the default `root` password. You're going to want to run `docker-compose logs peertube | grep -A1 root` to search the log output for your new PeerTube's instance admin credentials which will look something like this. You can also grep your peertube container's logs for the default `root` password. You're going to want to run `docker-compose logs peertube | grep -A1 root` to search the log output for your new PeerTube's instance admin credentials which will look something like this.
```bash ```bash
docker-compose logs peertube | grep -A1 root docker compose logs peertube | grep -A1 root
peertube_1 | [example.com:443] 2019-11-16 04:26:06.082 info: Username: root peertube_1 | [example.com:443] 2019-11-16 04:26:06.082 info: Username: root
peertube_1 | [example.com:443] 2019-11-16 04:26:06.083 info: User password: abcdefghijklmnop peertube_1 | [example.com:443] 2019-11-16 04:26:06.083 info: User password: abcdefghijklmnop
@ -142,19 +143,19 @@ Pull the latest images:
```shell ```shell
cd /your/peertube/directory cd /your/peertube/directory
docker-compose pull docker compose pull
``` ```
Stop, delete the containers and internal volumes (to invalidate static client files shared by `peertube` and `webserver` containers): Stop, delete the containers and internal volumes (to invalidate static client files shared by `peertube` and `webserver` containers):
```shell ```shell
docker-compose down -v docker compose down -v
``` ```
Rerun PeerTube: Rerun PeerTube:
```shell ```shell
docker-compose up -d docker compose up -d
``` ```
## Build ## Build