Package Details: peertube 2.0.0-1

Git Clone URL: (read-only)
Package Base: peertube
Description: Federated (ActivityPub) video streaming platform using P2P (BitTorrent) directly in the web browser with WebTorrent and Angular.
Upstream URL:
Keywords: p2p torrent video
Licenses: AGPL
Submitter: daftaupe
Maintainer: daftaupe (rigelk)
Last Packager: daftaupe
Votes: 11
Popularity: 0.006630
First Submitted: 2018-04-11 19:46
Last Updated: 2019-11-13 10:27

Latest Comments

1 2 Next › Last »

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.

rigelk commented on 2019-02-06 13:32

please double check the breaking changes present in the 1.2.0 release (mainly new configurations to add to your production.yaml):

mkoppmann commented on 2018-09-13 19:46

@rigelk: Awesome, thank you very much :)

rigelk commented on 2018-09-13 10:08

@mkoppmann: now fixed upstream - it was an incompatibility of bcrypt >= 3.x with Node 8.12 specifically (downgrading to Node 8.11.x solved the problem) - they made a new release and I updated accordingly.

mkoppmann commented on 2018-09-11 21:31

Can’t install this package currently. It fails at installing the bcrypt@3.0.0 module. This is because Nodejs 10 is required for that.