@matrix it does some fancy stuff with some files like logs and etc... so chrooting is not ideal
スプリットショックウイルス †
I've heard horror stories about Peertube with network storage. They only recommend using S3.
@splitshockvirus @matrix @splitshockvirus @matrix Yeah, I'm gonna go have to implement S3 along with S3 caching servers on all of my CDN nodes because there seems to be no way to properly cache byte range only in Nginx. For every 2 second byte range request of a video file, Nginx wants to download the entire MP4 video file from the backend.
That's completely unacceptable. Apparently there is a 3rd party plugin that supposedly fixes that but I can't be fucked to test it.
By the time I got it implemented I could have S3 storage implemented along with half the caching servers done which should solve my problem. At least in theory.
That's completely unacceptable. Apparently there is a 3rd party plugin that supposedly fixes that but I can't be fucked to test it.
By the time I got it implemented I could have S3 storage implemented along with half the caching servers done which should solve my problem. At least in theory.
Yeah object storage is something I'm eventually going to have to implement. It's not a pressing issue but it's not something I was to let go unchecked when I move to my own hypervisor.
The CDN is currently on my list of things to do, but I'm kind of out of my element on HA-Proxy tbh. I'd like to do an implementation like cloudflare but I'd have to host nameservers. Also I'm not sure how the caching is supposed to work with that.
Are you self-hosting your object storage or are you getting it from a provider?
@matrix
[jasmine ~]# grep null /etc/nginx/sites/peertube.conf
try_files /dev/null @api;
try_files /dev/null @api;
try_files /dev/null @api;
try_files /dev/null @api;
try_files /dev/null @api_websocket;
try_files /dev/null @api_websocket;
It's some quirk regarding the upstream directive, like the only way to access it is via try_files, and this guarantees it will always pass up there.
I tried to prove it wrong a couple weeks back or something because someone else rightly complained about it. I did not succeed.
[jasmine ~]# grep null /etc/nginx/sites/peertube.conf
try_files /dev/null @api;
try_files /dev/null @api;
try_files /dev/null @api;
try_files /dev/null @api;
try_files /dev/null @api_websocket;
try_files /dev/null @api_websocket;
It's some quirk regarding the upstream directive, like the only way to access it is via try_files, and this guarantees it will always pass up there.
I tried to prove it wrong a couple weeks back or something because someone else rightly complained about it. I did not succeed.
@Zerglingman Never would have thought /dev/null would be in the config
Oh cool, I fixed it. The permissions need to be 755, not 754