Package Details: peertube 3.0.1-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: rigelk
Votes: 16
Popularity: 0.44
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: https://keybase.io/chocobozzz

Latest Comments

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

rigelk commented on 2020-03-02 14:03

@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

@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

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

cgirard commented on 2020-02-24 15:13

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

ne-vlezay80 commented on 2019-07-11 16:40

`[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

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

@ALSimon, last push should fix your issue.

ALSimon commented on 2019-02-15 09:59

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

daftaupe commented on 2019-02-06 22:13

@ALSimon, the service file comes from upstream. You better check with the Peertube project directly.

ALSimon commented on 2019-02-06 22:03

Please change ProtectSystem=full to ProtectSystem=true in /usr/lib/systemd/system/peertube.service. With this package, configuration is intalled in /etc/peertube. With ProtectSystem=full, /etc/ is mounted as readonly and cannot be updated in admin UI.