Package Details: peertube 3.0.1-1

Git Clone URL: (read-only, click to copy)
Package Base: peertube
Description: ActivityPub-federated video streaming platform using P2P directly in your web browser
Upstream URL:
Keywords: hls p2p self-hosted torrent video
Licenses: AGPL
Submitter: daftaupe
Maintainer: daftaupe (rigelk)
Last Packager: rigelk
Votes: 17
Popularity: 0.77
First Submitted: 2018-04-11 19:46
Last Updated: 2021-01-12 11:21

Pinned Comments

rigelk commented on 2020-06-18 13:32

Please note that the package now verifies the release signature against the lead developer's key, which you can find here:

Latest Comments

1 2 3 4 Next › Last »

peter.babic commented on 2021-02-20 11:39

There is no folder /usr/share/webapps/peertube/dist/server/tools/, consequently the file /usr/bin/peertube won't run, because it wants to run peertube.js from that folder.

daftaupe commented on 2020-09-19 18:01

@rcrath, nodejs 14 is not supported yet so we have to keep the check in the package.

rcrath commented on 2020-09-15 04:20

fails because of conflict between need for "nodejs<13" and my installed version, nodejs 14, which will break other things if uninstalled.

rigelk commented on 2020-06-18 13:32

Please note that the package now verifies the release signature against the lead developer's key, which you can find here:

rigelk commented on 2020-06-18 13:30

@cgirard @ChrisMorgan thanks for your suggestions, I had not considered that possibility - I just updated the PKGBUILD to reflect the current support of PeerTube for nodejs versions.

ChrisMorgan commented on 2020-06-18 09:07

It would be better for it to depend not on nodejs-lts-dubnium or nodejs-lts-erbium, but on nodejs>=10, nodejs<13.

cgirard commented on 2020-06-18 09:05

Could you consider switching to nodejs-lts-erbium? It works fine as far as I can tell.

rigelk commented on 2020-05-30 08:36

@daftaupe @ChrisMorgan, we might just split have a second package peertube-dev to differentiate both options, if that sounds better.

daftaupe commented on 2020-05-30 08:19


rigelk removed the --production flag because "CLI dependencies are part of the development dependencies" and this is a really good reason. I haven't had the time to check if it's still needed now to get the admin tools to build (I'm only maintaining the package, I don't own an instance at the moment).

I didn't use .tar.xz because, for some reason, I couldn't build properly from it at the beginning, I can't remember what was wrong though.

I'll see about the !strip option when the next release is out.

Also I'm aware that there are issue with applying the configuration from the web interface, no need to add a comment on that.

ChrisMorgan commented on 2020-05-29 19:22

This package is positively enormous at present (approaching 2GB), and it doesn’t need to be.

Steps that should be taken:

  1. On the yarn install invocation, add --production per the official instructions. This saves a lot of download and installation time and 1GB of package size. That still leaves it at around 600MB, which is in my opinion atrociously large, but is what upstream gives you.

  2. Add options=('!strip'), because there are no binaries for it to strip but it takes ages going through all the zillions of files. (Sure, there are less after the previous step, but still a lot, and it takes a lot of time.)

There are other major opportunities for space savings which I’ve written up at

For the next release, I also believe you should be able to use the .tar.xz source instead of .zip, which halves the source download (saving 50MB). I’m guessing this wasn’t done in the past because the 2.1.1 .tar.xz looks too small to be realistic, so is something missing? Well, the 2.2.0-rc.1 release .tar.xz looks a realistic size relative to the zip file.