Package Details: peertube 7.2.0-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: 29
Popularity: 0.001668
First Submitted: 2018-04-11 19:46 (UTC)
Last Updated: 2025-06-11 11:54 (UTC)

Pinned Comments

daftaupe commented on 2025-06-11 11:52 (UTC)

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

daftaupe commented on 2025-03-18 19:49 (UTC)

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

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 7 Next › Last »

ChrisMorgan commented on 2020-05-29 19:22 (UTC)

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 https://github.com/Chocobozzz/PeerTube/issues/2807.

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.

cgirard commented on 2020-03-03 16:03 (UTC)

Thank you. I have just tested to build and run it with nodejs-lts-erbium and everything seems to work fine.

rigelk commented on 2020-03-02 14:03 (UTC)

@cgirard: I found time to update the package - directly to 2.1.1 - sorry about the delay!

cgirard commented on 2020-02-27 13:13 (UTC)

@rigelk: OK, no problem. If you need any help, let me know. In the meantime, 2.1.1 has been released

rigelk commented on 2020-02-24 17:07 (UTC)

@cgirard I simply didn't find time to update it yet.

cgirard commented on 2020-02-24 15:13 (UTC)

Hello @daftaupe and @rigelk is there anything blocking the update?

ne-vlezay80 commented on 2019-07-11 16:40 (UTC) (edited on 2019-07-11 16:41 (UTC) by ne-vlezay80)

`[peertube@peertube peertube]$ export NODE_CONFIG_DIR=/etc/peertube/
[peertube@peertube peertube]$ npm start

peertube@1.3.1 start /usr/share/webapps/peertube node dist/server

WARNING: No configurations found in configuration directory:/etc/peertube/ WARNING: To disable this warning set SUPPRESS_NO_CONFIG_WARNING in the environment. /usr/share/webapps/peertube/dist/server/initializers/config.js:211 throw new Error('Invalid config source.'); ^

Error: Invalid config source. at getLocalConfigFilePath (/usr/share/webapps/peertube/dist/server/initializers/config.js:211:15) at Object.<anonymous> (/usr/share/webapps/peertube/dist/server/initializers/config.js:9:18) at Module._compile (module.js:653:30) at Object.Module._extensions..js (module.js:664:10) at Module.load (module.js:566:32) at tryModuleLoad (module.js:506:12) at Function.Module._load (module.js:498:3) at Module.require (module.js:597:17) at require (internal/module.js:11:18) at Object.<anonymous> (/usr/share/webapps/peertube/dist/server/helpers/logger.js:6:18) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! peertube@1.3.1 start: node dist/server npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the peertube@1.3.1 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.`

rigelk commented on 2019-02-25 15:09 (UTC) (edited on 2019-02-25 15:11 (UTC) by rigelk)

I just added dependencies required for the remote tools to work. Sadly, it increases the package size a lot (since CLI dependencies are part of the development dependencies), but until that is mitigated upstream, that is the only way.

Now at least we can all use the CLI :)

daftaupe commented on 2019-02-20 14:28 (UTC)

@ALSimon, last push should fix your issue.

ALSimon commented on 2019-02-15 09:59 (UTC)

@daftaupe, on upstream source, the configuration file is in peertube directory, not in /etc. So they don't need to access /etc and can use ProtectSystem=full. It's arch's PKGBUILD which ask to move the config file to /etc and may change ProtectSystem for this working.