1
0
Fork 0

Update changelog

This commit is contained in:
Chocobozzz 2024-09-18 14:13:56 +02:00
parent 606493f3ad
commit bde9a488ae
No known key found for this signature in database
GPG key ID: 583A612D890159BE

View file

@ -4,11 +4,11 @@
### IMPORTANT NOTES
* **Important** You need to manually execute a migration script after your upgrade while PeerTube is running.
* **Important** You need to manually execute a migration script after your upgrade while PeerTube is running and the database migration is complete (`Migrations finished. New migration version schema: 865` in PeerTube startup logs, this migration script may take a while).
The purpose of this migration is to update video files metadata in the database.
This migration can take a long time if you have many federated/local videos, but is designed to be safe to run multiple times:
* Classic installation: `cd /var/www/peertube/peertube-latest && sudo -u peertube NODE_CONFIG_DIR=/var/www/peertube/config NODE_ENV=production node dist/scripts/migrations/peertube-6.3.js`
* Docker installation: `cd /var/www/peertube-docker && docker-compose exec -u peertube peertube node dist/scripts/migrations/peertube-6.3.js`
* Docker installation: `cd /var/www/peertube-docker && docker compose exec -u peertube peertube node dist/scripts/migrations/peertube-6.3.js`
* **Important for Docker admins** If you enabled the "Keep a version of the input file" configuration, files may have been stored in the container instead of the host volume. To prevent data loss, you must **copy** the files on the host before upgrading using `docker compose cp peertube:/app/storage/original-video-files docker-volume/data`
### Docker