I also put the video itself into a S3 bucket, so PeerTube basically only has to show the meta data and the comments from my server, so kind of like what Mastodon or Lemmy/PieFed has to do. I just had a look at the [PeerTube nginx config((https://github.com/Chocobozzz/PeerTube/blob/develop/support/nginx/peertube) but couldn’t see anything there which would do caching, so I assume the app does it’s own caching somewhere.
For my website, which is a rails application, I did
I had the problem that peertube redundancy only works on public videos and most of my videos are private/internal. And in my specific case I hosted them in Germany where my server is and because of routing and peering they would always buffer a lot in South Korea where I am so I had to solve it in a creative way, the S3 bucket is one part of my solution, putting it in the right country was another, which I explain in detail here: https://tube.jeena.net/w/uXZN52xsH75LbHWNt8dsLY
How does peertube cache? I know it P2P the video which is nice in case anything goes viral, but I never took the time to figure out any caching.
My tiny single digit user instance seems to keep up with any traffic on a equivalent of a pi…so I assume its good .
I also put the video itself into a S3 bucket, so PeerTube basically only has to show the meta data and the comments from my server, so kind of like what Mastodon or Lemmy/PieFed has to do. I just had a look at the [PeerTube nginx config((https://github.com/Chocobozzz/PeerTube/blob/develop/support/nginx/peertube) but couldn’t see anything there which would do caching, so I assume the app does it’s own caching somewhere.
For my website, which is a rails application, I did
proxy_cache_path /var/lib/nginx/cache/jeena.net keys_zone=jeenanet:30m;and then
location @rails { # ... proxy_cache jeenanet; }Nice! Yeah the S3 is a good way to work with it. They are dirt cheap at least.
…I should probably upgrade my setup at some point haha.
I had the problem that peertube redundancy only works on public videos and most of my videos are private/internal. And in my specific case I hosted them in Germany where my server is and because of routing and peering they would always buffer a lot in South Korea where I am so I had to solve it in a creative way, the S3 bucket is one part of my solution, putting it in the right country was another, which I explain in detail here: https://tube.jeena.net/w/uXZN52xsH75LbHWNt8dsLY