@LoudLemur said in Professional PeerTube Installation:

Using Cloudron, how could we offer OIDC logins for e.g. PeerTube?

We already have this:

4fef5a72-4953-4577-9226-66d337aef1fd-image.png

As far as I understood, those are all optional and you can set them as you like. However one storage related change was required and I've put that into the start.sh to get added.

Yep. Bunny has those too.
You can encrypt the videos for each session.
You restrict the videos to play on only some domains etc.

@scooke you could also experiment with taking off the https:// from your endpoint as I don't think that's supposed to be there 🙂

I found the issue with some help from their Git. I'm posting it here because it's not well-documented and doesn't seem to be mentioned anywhere else. (EDIT: Hats off to the dev, who upon seeing my Git post went and updated the documentation to specifically recommend reviewing this directive!)

Peertube DOES throttle network speed! A fresh install is limited to 5 MB/s. This is fine for 1080P but barely adequate for typical 30 FPS 4K footage, and unworkable for high-quality 4K or 4K at 60 FPS. For perspective, YouTube recommends nearly 9 MB/s for 60FPS 4K video.

You can adjust this hard limit by modifying peertube.conf and adjusting the values listed below:

You should take your network performance, desired video quality, and download functionality into consideration before modifying these. For most people, 10M should give you ample 4K quality without excessive buffering. If you want to allow downloads, consider setting them to 25M or higher.

I'm glad this wasn't a Cloudron issue, but I appreciate the effort of anyone who took the time to stop and think about this one. I suspect this value was different in previous versions and carries over with upgrades; this may only affect new installations.

I fixed the docs, thanks for reporting.

@LoudLemur said in How to setup Object Storage for Peertube on Cloudron (iDrive e2):

Do you think this might be to enable other instances following / subscribing to your own, so they might need access to those files?

Good question, possibly, but I've really no idea.

Try subscribing to https://uniteddiversity.tv and/ or https://bridport.tv and let's see what happens...?

@jdaviescoates Good catch, I meant AWS S3 as that seems to be the standard and most tuts use that, and most S3-compatible also use similar phrasing for their options, but as the number of posts eve just here on this forum say, non AWS S3 is a crapshoot.

@shrey great work figuring the root cause! I have published a new package now that highlights the breaking changes in 6.0 .

For others reading, the main issue was that some of the configuration keys have changed in peertube 6. See https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md#v600 for more information. For example, if you use object storage to store videos, the storage paths have changed.

@girish said in Peertube audio-only transcoding with HLS, AV1, VP9 Transcoding - 2024 roadmap:

Hardware support for transcoding is a different beast though (of which I don't have much idea about)

On AMD, RDNA3 capable CPUs can do great transcoding. Contabo have AMD Ryzen 9 7900 VPS which can do AV1 encode.

Peertube also supports runners, so you can send your transcoding to another server for transcoding. There is some great new kit for video transcoding now:

https://www.xilinx.com/applications/data-center/video-imaging/alveo-ma35d.html

@robi said in How to run these Peertube CLI commands to move videos to object storage on Cloudron?:

@LoudLemur If you contribute one, it can be added.

I suppose I could make a video for it, but it would be more like a Laurel and Hardy "How not to..." than a "How to...", I think! Custard pies, planks of wood and banana skins everywhere!

They have renamed a bunch of storage related parameters which will break existing installations. So, we have to make a major release.

@AartJansen Good idea, I will bump the default memory limit.

@mdc773 said in Regenerate video thumbnails:

i don't fully understand max upload part

On S3 compatible storage, you can upload large files, like 5TB. It would be infeasible to upload such large files in a single shot. So, they have APIs to upload files in "parts". Like you upload 10k parts of 5GB each for example to get to 5TB. The number of parts and size of each part depends on the S3 storage.

Usually, I leave upload part size to something like 10MB-50MB. There is actually nothing wrong with 100MB part size, but for some reason peertube is complaining about it.

I wish It could be used like for the LAMP containers, apache handling the file access, I'm using it a lot in that context and it works perfectly ! but yeah I get it 🙂