From 3ead9195c9db831aea9904806ea6409e3aef06a9 Mon Sep 17 00:00:00 2001 From: "The repo.or.cz admin team" Date: Wed, 2 Sep 2020 22:50:49 +0200 Subject: [PATCH] Girocco/Config.pm: set some repository limits The site terms and conditions (repo.or.cz/about.html) have always specified size limits on hosted repositories. Start to enforce some limits automatically in order to avoid causing any unwanted negative service impacts. Signed-off-by: The repo.or.cz admin team --- Girocco/Config.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Girocco/Config.pm b/Girocco/Config.pm index c49b5d0..310f910 100644 --- a/Girocco/Config.pm +++ b/Girocco/Config.pm @@ -817,7 +817,7 @@ our %reserved_suffixes = ( # The value represents the maximum file size allowed in units of 512-byte blocks # and must be <= 2147483647 (which represents a size of 1 TiB less 512 bytes). # -our $max_file_size512 = undef; # default is no limit +our $max_file_size512 = 8388608; # 4 GiB # If this is set to a non-zero value, after an otherwise successful clone, # if the repository contains more than this many objects, the clone will @@ -827,7 +827,7 @@ our $max_file_size512 = undef; # default is no limit # means that if $max_file_size512 is non-zero that the resulting clone did # not exceed the file size limit if it fails this check. # -our $max_clone_objects = undef; # default is no limit +our $max_clone_objects = 9999999; # -- 2.11.4.GIT