Package Details: peertube 6.0.4-1

Git Clone URL: https://aur.archlinux.org/peertube.git (read-only, click to copy)
Package Base: peertube
Description: ActivityPub-federated video streaming platform using P2P directly in your web browser
Upstream URL: https://joinpeertube.org/
Keywords: hls p2p self-hosted torrent video
Licenses: AGPL
Submitter: daftaupe
Maintainer: daftaupe (rigelk)
Last Packager: daftaupe
Votes: 28
Popularity: 0.159387
First Submitted: 2018-04-11 19:46 (UTC)
Last Updated: 2024-04-04 20:07 (UTC)

Pinned Comments

daftaupe commented on 2023-12-17 09:27 (UTC) (edited on 2023-12-17 09:32 (UTC) by daftaupe)

Please read and follow the release notes from 6.0.0 to 6.0.2.

A lot of changes in configuration files are required, too many to list here. Also please note that /var/lib/peertube/storage/videos is now /var/lib/peertube/storage/web-videos to match the move from storage.videos to storage.web-videos.

Please test and let me know.

rigelk commented on 2020-06-18 13:32 (UTC)

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

daftaupe commented on 2022-11-29 21:19 (UTC)

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

kauron commented on 2022-09-22 12:00 (UTC) (edited on 2022-09-22 12:03 (UTC) by kauron)

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.

dodecahedron commented on 2022-08-17 20:04 (UTC)

@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.

daftaupe commented on 2022-08-11 17:09 (UTC) (edited on 2022-08-11 17:14 (UTC) by daftaupe)

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.

dodecahedron commented on 2022-04-19 21:44 (UTC)

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)

kauron commented on 2022-04-13 12:59 (UTC)

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?

daftaupe commented on 2021-12-20 08:55 (UTC)

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.

rcrath commented on 2021-12-16 04:44 (UTC)

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.

daftaupe commented on 2021-12-15 09:01 (UTC)

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

dodecahedron commented on 2021-12-15 01:06 (UTC)

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.

« First ‹ Previous 1 2 3 4 5 6 Next › Last »