5 # Correspond to your reverse proxy server_name/listen configuration
8 hostname: 'example.com'
13 # 15 attempts in 5 min
21 # Proxies to trust to get real client IP
22 # If you run PeerTube just behind a local proxy (nginx), keep 'loopback'
23 # If you run PeerTube behind a remote proxy, add the proxy IP address (or subnet)
27 # Your database name will be "peertube"+database.suffix
37 # Redis server for short time storage
38 # You can also specify a 'socket' path to a unix socket but first need to
39 # comment out hostname and port
46 # SMTP server to send emails
49 port: 465 # If you use StartTLS: 587
52 tls: true # If you use StartTLS: false
53 disable_starttls: false
54 ca_file: null # Used for self signed certificates
55 from_address: 'admin@example.com'
57 # From the project root directory
59 tmp: '/var/www/peertube/storage/tmp/' # Used to download data (imports etc), store uploaded files before processing...
60 avatars: '/var/www/peertube/storage/avatars/'
61 videos: '/var/www/peertube/storage/videos/'
62 streaming_playlists: '/var/www/peertube/storage/streaming-playlists/'
63 redundancy: '/var/www/peertube/storage/videos/'
64 logs: '/var/www/peertube/storage/logs/'
65 previews: '/var/www/peertube/storage/previews/'
66 thumbnails: '/var/www/peertube/storage/thumbnails/'
67 torrents: '/var/www/peertube/storage/torrents/'
68 captions: '/var/www/peertube/storage/captions/'
69 cache: '/var/www/peertube/storage/cache/'
72 level: 'info' # debug/info/warning/error
75 # Add ability to fetch remote videos/actors by their URI, that may not be federated with your instance
76 # If enabled, the associated group will be able to "escape" from the instance follows
77 # That means they will be able to follow channels, watch videos, list videos of non followed instances
84 interval_days: 7 # Compute trending videos for the last x days
86 # Cache remote videos on your server, to help other instances to broadcast the video
87 # You can define multiple caches using different sizes/strategies
88 # Once you have defined your strategies, choose which instances you want to cache in admin -> manage follows -> following
91 check_interval: '1 hour' # How often you want to check new videos to cache
92 strategies: # Just uncomment strategies you want
95 # # Minimum time the video must remain in the cache. Only accept values > 10 hours (to not overload remote instances)
96 # min_lifetime: '48 hours'
97 # strategy: 'most-views' # Cache videos that have the most views
100 # # Minimum time the video must remain in the cache. Only accept values > 10 hours (to not overload remote instances)
101 # min_lifetime: '48 hours'
102 # strategy: 'trending' # Cache trending videos
105 # # Minimum time the video must remain in the cache. Only accept values > 10 hours (to not overload remote instances)
106 # min_lifetime: '48 hours'
107 # strategy: 'recently-added' # Cache recently added videos
108 # min_views: 10 # Having at least x views
112 report_only: true # CSP directives are still being tested, so disable the report only mode at your own risk!
116 # If you disable the tracker, you disable the P2P aspect of PeerTube
118 # Only handle requests on your videos.
119 # If you set this to false it means you have a public tracker.
120 # Then, it is possible that clients overload your instance with external torrents
122 # Reject peers that do a lot of announces (could improve privacy of TCP/UDP peers)
123 reject_too_many_announces: false
127 # If you want to limit users videos history
128 # -1 means there is no limitations
129 # Other values could be '6 months' or '30 days' etc (PeerTube will periodically delete old entries from database)
134 # PeerTube creates a database entry every hour for each video to track views over a period of time
135 # This is used in particular by the Trending page
136 # PeerTube could remove old remote video views if you want to reduce your database size (video view counter will not be altered)
137 # -1 means no cleanup
138 # Other values could be '6 months' or '30 days' etc (PeerTube will periodically delete old entries from database)
143 ###############################################################################
145 # From this point, all the following keys can be overridden by the web interface
146 # (local-production.json file). If you need to change some values, prefer to
147 # use the web interface because the configuration will be automatically
148 # reloaded without any need to restart PeerTube.
150 # /!\ If you already have a local-production.json file, the modification of the
151 # following keys will have no effect /!\.
153 ###############################################################################
157 size: 500 # Max number of previews you want to cache
159 size: 500 # Max number of video captions/subtitles you want to cache
162 # Used to generate the root user at first startup
163 # And to receive emails from the contact form
164 email: 'admin@example.com'
171 limit: 10 # When the limit is reached, registrations are disabled. -1 == unlimited
172 requires_email_verification: false
174 cidr: # You can specify CIDR ranges to whitelist (empty = no filtering) or blacklist
179 # Default value of maximum video BYTES the user can upload (does not take into account transcoded files).
182 video_quota_daily: -1
184 # If enabled, the video will be transcoded to mp4 (x264) with "faststart" flag
185 # In addition, if some resolutions are enabled the mp4 video file will be transcoded to these new resolutions.
186 # Please, do not disable transcoding since many uploaded videos will not work
189 # Allow your users to upload .mkv, .mov, .avi, .flv videos
190 allow_additional_extensions: true
192 resolutions: # Only created if the original video has a higher resolution, uses more storage!
198 # /!\ EXPERIMENTAL /!\
199 # /!\ Requires ffmpeg >= 4
200 # Generate HLS playlists and fragmented MP4 files. Better playback than with WebTorrent:
201 # * Resolution change is smoother
202 # * Faster playback in particular with long videos
203 # * More stable playback (less bugs/infinite loading)
204 # /!\ Multiplies videos storage by 2 /!\
209 # Add ability for your users to import remote videos (from YouTube, torrent...)
211 http: # Classic HTTP or all sites supported by youtube-dl https://rg3.github.io/youtube-dl/supportedsites.html
213 torrent: # Magnet URI or torrent file (use classic TCP/UDP/WebSeed to download the file)
217 # New videos automatically blacklisted so moderators can review before publishing
225 short_description: 'PeerTube, a federated (ActivityPub) video streaming platform using P2P (BitTorrent) directly in the web browser with WebTorrent and Angular.'
226 description: '' # Support markdown
227 terms: '' # Support markdown
228 default_client_route: '/videos/trending'
229 # Whether or not the instance is dedicated to NSFW content
230 # Enabling it will allow other administrators to know that you are mainly federating sensitive content
231 # Moreover, the NSFW checkbox on video upload will be automatically checked by default
233 # By default, "do_not_list" or "blur" or "display" NSFW videos
234 # Could be overridden per user with a setting
235 default_nsfw_policy: 'do_not_list'
237 javascript: '' # Directly your JavaScript code (without <script> tags). Will be eval at runtime
238 css: '' # Directly your CSS code (without <style> tags). Will be injected at runtime
239 # Robot.txt rules. To disallow robots to crawl your instance and disallow indexation of your site, add '/' to "Disallow:'
243 # Security.txt rules. To discourage researchers from testing your instance and disable security.txt integration, set this to an empty string.
245 "# If you would like to report a security issue\n# you may report it to:\nContact: https://github.com/Chocobozzz/PeerTube/blob/develop/SECURITY.md\nContact: mailto:"
248 # You can provide a reporting endpoint for Content Security Policy violations
250 # Cards configuration to format video in Twitter
252 username: '@Chocobozzz' # Indicates the Twitter account for the website or platform on which the content was published
253 # If true, a video player will be embedded in the Twitter feed on PeerTube video share
254 # If false, we use an image link card that will redirect on your PeerTube instance
255 # Test on https://cards-dev.twitter.com/validator to see if you are whitelisted
260 # Allow or not other instances to follow yours
262 # Whether or not an administrator must manually validate a new follower
263 manual_approval: false