Arch Linux User Repository

7.2.0 is out, check the release notes. Biggest point is to run a migration script : cd /usr/share/webapps/peertube && sudo -u peertube NODE_CONFIG_DIR=/etc/peertube NODE_ENV=production node dist/scripts/migrations/peertube-7.2.js

7.1.0 is out, check the release notes. One important note is : "Due to a bug in the remote video thumbnail update, we recommend running the prune storage script to clean up the filesystem".

Please note that the package now verifies the release signature against the lead developer's key, which you can find here: https://keybase.io/chocobozzz

The following migration scrip thas to be run on a running instance after upgrading to 4.2.2 (part of 4.2.0 upgrade) cd /usr/share/webapps/peertube/ && sudo -u peertube NODE_CONFIG_DIR=/etc/peertube NODE_ENV=production node dist/scripts/migrations/peertube-4.2.js

Adapted from the official release announce

Sorry for being so late guys, but I don't have a running instance anymore and am rather busy.

Also I had to install nodejs-lts-gallium to be install to build 4.2.2, one NodeJS package requires a version not greater than 17.

I have the same issue. nginx is unable to access any of the PeerTube files so all the images on my instance are not loading. The peertube.tmpfiles file was introduced in this commit and should probably modified to mode 0755 or at least 0750. (With mode 0750, you can add nginx to the peertube group)

I think that there is an error with my configuration or with peertube.tmpfiles: the folders within /var/lib/peertube/storage have mode 0700 and are inaccessible to nginx. Is nginx supposed to run under the peertube user? Or should the tmpfiles configuration set the mode to 0701?

It should now be possible to use latest nodejs instead of the lts versions only. That message makes it more obvious than just bumping the release version of the package, I realize.

Thanks for maintaining this important package @daftaupe. Since it actually compiles under 17, and it is arch, which always uses the latest pretty quickly, as opposed to Debian, etc, would it be possible to bump the release number? I hated replacing my whole nodejs with the LTS as it does not seem to be within my skills to install and run both. So far, it has not broken anything but since arch is bleeding edge, maybe you would consider an exception to upstream since it does in fact compile with 17 according to @Ta180m? Thanks for considering.

The documentation at https://docs.joinpeertube.org/dependencies states the following only LTS versions of external dependencies are supported.

Is there any reason why this package requires an LTS version of Node.js? I compiled it with Node.js 17 and it seems to work fine and I'm pretty sure upstream supports all Node versions above and including 12.

The following migration script has to be run on a running instance after moving to 4.0.0 cd /usr/share/webapps/peertube/ && sudo -u peertube NODE_CONFIG_DIR=/etc/peertube NODE_ENV=production node dist/scripts/migrations/peertube-4.0.js

Adapted from the official release announce

Seems it needs nodejs<16 instead of nodejs<=15 for dependency resolution to correctly works.

[localhost:443] 2021-03-12 01:39:15.518 info: Database peertube_prod is ready. [localhost:443] 2021-03-12 01:39:15.526 error: Cannot install application. { "err": { "stack": "Error: ENOENT: no such file or directory, mkdir", "message": "ENOENT: no such file or directory, mkdir", "errno": -2, "code": "ENOENT", "syscall": "mkdir" } }