From 64427abbea0c28f803e944e88c60c535c500e68b Mon Sep 17 00:00:00 2001 From: anmol26s Date: Wed, 3 Oct 2018 14:25:36 +0530 Subject: [PATCH] Removed reduency from producton.yaml --- conf/production.yaml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/conf/production.yaml b/conf/production.yaml index c7e2b48..c827ef9 100644 --- a/conf/production.yaml +++ b/conf/production.yaml @@ -71,10 +71,10 @@ trending: # 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 -redundancy: - videos: - check_interval: '6 hour' # How often you want to check new videos to cache - strategies: +#redundancy: +# videos: +# check_interval: '6 hour' # How often you want to check new videos to cache +# strategies: # - # size: '10GB' # strategy: 'most-views' # Cache videos that have the most views @@ -82,11 +82,11 @@ redundancy: # size: '10GB' # strategy: 'trending' # Cache trending videos # - - size: '1GB' +# size: '1GB' # Minimum time the video must remain in the cache. Only accept values > 10 hours (to not overload remote instances) - min_lifetime: '48 hours' - strategy: 'recently-added' # Cache recently added videos - minViews: 10 # Having at least x views +# min_lifetime: '48 hours' +# strategy: 'recently-added' # Cache recently added videos +# minViews: 10 # Having at least x views