Package Details: peertube 6.1.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: 28
Popularity: 0.084741
First Submitted: 2018-04-11 19:46 (UTC)
Last Updated: 2024-04-29 14:00 (UTC)

Pinned Comments

daftaupe commented on 2024-04-29 14:00 (UTC)

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.

daftaupe commented on 2023-12-17 09:27 (UTC) (edited on 2023-12-17 09:32 (UTC) by daftaupe)

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.

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

ChrisMorgan commented on 2020-06-18 09:07 (UTC) (edited on 2020-06-18 09:07 (UTC) by ChrisMorgan)

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 (UTC)

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 (UTC)

@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 (UTC) (edited on 2020-05-30 08:36 (UTC) by daftaupe)

@ChrisMorgan,

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 (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?