Arch Linux User Repository

As usual please read the release notes for 6.1.0. Most notable thing is you must add a location ~ ^/api/v1/users/[^/]+/imports/import-resumable$ { block in the nginx config.

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.

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

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

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 :)

@ALSimon, last push should fix your issue.

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

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

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.

please double check the breaking changes present in the 1.2.0 release (mainly new configurations to add to your production.yaml): https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md#v120

@rigelk: Awesome, thank you very much :)

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

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.

https://www.npmjs.com/package/bcrypt#version-compatibility