…service * Allow option for overriding the maximum byte size POST limit
This change tests first for the existence of the custom config variable and then the existence of each custom config file in turn. If found the directory path to append to that config file is changed to the custom path. This allows fallback to the standard config when no custom config is present. Maybe it would be even better to load both - the standard config, then the custom config, but this might be confusing for groupConfig.php. It could work using array merge, but it wouldn't be particularly clear or easy to explain.
To allow "clean" checkouts of Minify we could use the possibility to define a custom config directory outside the minify directory. Using this patch a user can define MINIFY_CUSTOM_CONFIG_DIR on a new page outside the minify directory and then include minify's index.php on that page and point their rewrites etc. there instead. The config.php (and config-test.php) could be copied to the custom directory and edited without causing svn:external/git:submodule conflicts.