peertube.conf overwritten on restart
-
In order to reliably stream 4K, I have to adjust three rate limiter settings settings in /etc/nginx/sites-enabled/peertube.conf. As shipped PeerTube limits the speed to 5 Mb/s, and recommends site admins review this setting in their post-install guide.
A 4K 60 FPS video with moderate compression can easily have a bitrate of around 50 - 75 Mb/s, so I typically set this value to around 150M to allow ample elbow room. But when I restart the service, all my changes are overwritten. The site becomes unusable because any 4K video begins to stutter badly.
I don't have this issue with my previous freestanding installation nor my YunoHost installation, so I assume Cloudron is pulling a default config file from somewhere. Is there any way to make my changes to this file persistent? On the host systems I do see multiple copies of peertube.conf and nginx.conf located at many different folders with paths like /var/lib/docker/overlay2/long_alphanumeric_string/, but as Docker isn't my forte, I'm not sure what I should and should not be modifying to do things "correctly".
Thanks!
UPDATE: I just noticed that the nginx.conf file is not writeable, even as root. But there has to be some way to modify the file. What's the correct way to do so?
-
In order to reliably stream 4K, I have to adjust three rate limiter settings settings in /etc/nginx/sites-enabled/peertube.conf. As shipped PeerTube limits the speed to 5 Mb/s, and recommends site admins review this setting in their post-install guide.
A 4K 60 FPS video with moderate compression can easily have a bitrate of around 50 - 75 Mb/s, so I typically set this value to around 150M to allow ample elbow room. But when I restart the service, all my changes are overwritten. The site becomes unusable because any 4K video begins to stutter badly.
I don't have this issue with my previous freestanding installation nor my YunoHost installation, so I assume Cloudron is pulling a default config file from somewhere. Is there any way to make my changes to this file persistent? On the host systems I do see multiple copies of peertube.conf and nginx.conf located at many different folders with paths like /var/lib/docker/overlay2/long_alphanumeric_string/, but as Docker isn't my forte, I'm not sure what I should and should not be modifying to do things "correctly".
Thanks!
UPDATE: I just noticed that the nginx.conf file is not writeable, even as root. But there has to be some way to modify the file. What's the correct way to do so?
@vividly8450 have you seen https://docs.cloudron.io/apps/peertube/ ?
It says there:
Customization
Use the File manager to edit custom configuration under /app/data/production.yaml
Does that work?
-
@vividly8450 have you seen https://docs.cloudron.io/apps/peertube/ ?
It says there:
Customization
Use the File manager to edit custom configuration under /app/data/production.yaml
Does that work?
@jdaviescoates Unfortunately those are the PeerTube configuration options, which you'd normally set through the web interface. Rate limiting (specifically, the limit_rate and proxy_limit_rate directives) are set through the nginx configuration file at /etc/nginx/sites-enabled/peertube.conf, and there doesn't appear to be any way to access that through the file manager.
Interestingly enough I was previously able to modify this file to solve this issue (see here), but it appears something has changed since then.
