Arch Linux User Repository

7.0.0 is out, check the release notes.

Too many things to check to make a summary here, please read what's important to check.

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

Fails to run

peertube                                                      
node:internal/modules/cjs/loader:1147
  throw err;
  ^

Error: Cannot find module '/usr/share/webapps/peertube/dist/server/tools/peertube.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1144:15)
    at Module._load (node:internal/modules/cjs/loader:985:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:135:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v21.2.0

From the official relase notes of 5.2.0, make sure that :
- you update your nginx configuration to support remote runners: https://github.com/Chocobozzz/PeerTube/blob/develop/support/nginx/peertube#L101
- you add storage.tmp_persistent directory in configuration file. You must configure it in your production.yaml: https://github.com/Chocobozzz/PeerTube/blob/develop/config/production.yaml.example#L128

The official Release notes of 5.0.0 ask to run the following command cd /usr/share/webapps/peertube && sudo -u peertube NODE_CONFIG_DIR=/etc/peertube NODE_ENV=production node dist/scripts/migrations/peertube-5.0.js

@daftaupe Can you change the Python 2 dependency to Python 3 since PeerTube can use either one and Python 2 has been removed from the official Arch repos?

The PeerTube docs recommend using --production for yarn install so can you also make that edit to the PKGBUILD?

I've added yarn as a runtime dependency as per kauron comment.

For anyone experiencing an error after updating to 4.3.0 due to yarn not being installed (logs say can't run yarn install --pure-lockfile regarding "Registering plugins and themes"), or the file /var/lib/peertube/storage/tmp/plugins-global.css being missing, installing yarn solves the issue. I don't know if it must be kept around, but maybe it should be added as a runtime dependency.

@daftaupe If you don't have much time to maintain this package, could you add me as a co-maintainer?

I was able to build this using the latest nodejs by setting --install.ignore-engines true in my ~/.yarnrc.

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?