Migrating from environment variables to production.yaml

Hello,

I’ve initially configured my PeerTube instance using Docker environment variables as per the Docker tutorial [1]. Since this worked I never set up a default.yaml/production.yaml (as mentioned in the Any OS tutorial [2]). But now I’d like to change video_channel_synchronization.full_sync_videos_limit [3] option to sync channels with more than 1’000 videos.

As per the file load order [4] (mentioned here [5]) the way to go would be to migrate all PEERTUBE_* config options that I currently set through environment variables over to the production.yaml and delete the environment variables, since values in the production.yaml will always be preferred over environment variables, right?

Also I should be able to mount the production.yaml and default.yaml files as read-only, since options set in the Web-UI are saved in the local-production.json, right?

Best regards and thanks a lot for the help!
Also sorry for the link formatting, otherwise I couldn’t post all the references…

[1] https:// docs . joinpeertube . org/install/docker#get-the-latest-env-file
[2] https:// docs . joinpeertube . org/install/any-os#peertube-configuration
[3] https:// raw . githubusercontent . com/Chocobozzz/PeerTube/refs/heads/develop/config/production.yaml.example#:~:text=full_sync_videos_limit
[4] https:// github . com/node-config/node-config/wiki/Configuration-Files#file-load-order
[5] https:// docs . joinpeertube . org/maintain/configuration#peertube-configuration