peertube: bump to v7.2.0, helm chart v0.4.3

peertube/Chart.yaml

@@ -11,5 +11,5 @@ dependencies:
   repository: https://charts.bitnami.com/bitnami
   version: 20.6.0
 type: application
-version: 0.4.2
-appVersion: 7.1.0
+version: 0.4.3
+appVersion: 7.2.0

peertube/values.yaml

@@ -8,7 +8,7 @@ image:
   repository: chocobozzz/peertube
   pullPolicy: IfNotPresent
   # Overrides the image tag whose default is the chart appVersion.
-  tag: "v7.1.0-bookworm"
+  tag: "v7.2.0-bookworm"
 
 imagePullSecrets: []
 nameOverride: ""
@@ -223,6 +223,8 @@ configAsCode:
       # If you're using such a provider then you can increase this value
       max_request_attempts: 3
       streaming_playlists:
+        # Bucket name created on your object storage provider
+        # PeerTube will access it via {bucket_name}.example.com
         bucket_name: 'streaming-playlists'
         # Allows setting all buckets to the same value but with a different prefix
         prefix: '' # Example: 'streaming-playlists:'
@@ -233,7 +235,7 @@ configAsCode:
         # which can be a problem depending on your object storage provider
         # You can also choose to disable this feature to reduce live streams latency
         # Live stream replays are not affected by this setting, so they are uploaded in object storage as regular VOD videos
-        store_live_streams: true
+        store_live_streams: false
       web_videos:
         bucket_name: 'web-videos'
         prefix: ''
@@ -294,7 +296,7 @@ configAsCode:
             - 'hot' # Adaptation of Reddit's 'Hot' algorithm
             - 'most-viewed' # Number of views in the last x days
             - 'most-liked' # Global views since the upload of the video
-          default: 'most-viewed'
+          default: 'hot'
     # Cache remote videos on your server, to help other instances to broadcast the video
     # You can define multiple caches using different sizes/strategies
     # Once you have defined your strategies, choose which instances you want to cache in admin -> manage follows -> following
@@ -468,6 +470,15 @@ configAsCode:
       stun_servers:
         - 'stun:stunserver2024.stunprotocol.org'
         - 'stun:stun.framasoft.org'
+    nsfw_flags_settings:
+      # Allow logged-in/anonymous users to have a more granular control over their NSFW policy
+      # using NSFW flags (violent content, etc.) set by video authors
+      enabled: true
+    download_generate_video:
+      # Max parallel downloads on your instance
+      # Each download spawns an ffmpeg process
+      # The ffmpeg process ends when users have downloaded the entire file or cancelled the download
+      max_parallel_downloads: 100
     ###############################################################################
     #
     # From this point, all the following keys can be overridden by the web interface
@@ -826,7 +837,7 @@ configAsCode:
       # Enabling it will allow other administrators to know that you are mainly federating sensitive content
       # Moreover, the NSFW checkbox on video upload will be automatically checked by default
       is_nsfw: false
-      # By default, `do_not_list` or `blur` or `display` NSFW videos
+      # By default, `do_not_list`, `blur`, `warn` or `display` NSFW videos
       # Could be overridden per user with a setting
       default_nsfw_policy: 'display'
       # PeerTube uses this setting to explain to your users which law they must follow in the "About" instance pages