[Rt-commit] rt branch, 4.4/siteconfig.d, updated. rt-4.2.3-205-g4ea3ab4

[? sunnavy]

The branch, 4.4/siteconfig.d has been updated
       via  4ea3ab4e39810ea0b49b79acade00abbb321c567 (commit)
       via  7b5bc87d35b872cb28aea6da6dfb251d6fed393b (commit)
      from  ec24ba46f8421fe8d46119a6dd551c87ba953388 (commit)

Summary of changes:
 docs/UPGRADING-4.4               | 6 ++++++
 etc/RT_SiteConfig.d/Extension.pm | 4 ++++
 etc/RT_SiteConfig.pm             | 3 +++
 lib/RT/Config.pm                 | 6 +++++-
 4 files changed, 18 insertions(+), 1 deletion(-)
 create mode 100644 etc/RT_SiteConfig.d/Extension.pm

- Log -----------------------------------------------------------------
commit 7b5bc87d35b872cb28aea6da6dfb251d6fed393b
Author: sunnavy <sunnavy at bestpractical.com>
Date:   Fri Jun 27 18:51:26 2014 +0800

    typo

diff --git a/lib/RT/Config.pm b/lib/RT/Config.pm
index 995d7e3..5253d45 100644
--- a/lib/RT/Config.pm
+++ b/lib/RT/Config.pm
@@ -88,7 +88,7 @@ Second file is F<RT_SiteConfig.pm> - site config file. You can use it
 to customize your RT instance. In this file you can override any option
 listed in core config file.
 
-RT extensions could also provide thier config files. Extensions should
+RT extensions could also provide their config files. Extensions should
 use F<< <NAME>_Config.pm >> and F<< <NAME>_SiteConfig.pm >> names for
 config files, where <NAME> is extension name.
 

commit 4ea3ab4e39810ea0b49b79acade00abbb321c567
Author: sunnavy <sunnavy at bestpractical.com>
Date:   Fri Jun 27 19:04:33 2014 +0800

    add an example and document SiteConfig.d

diff --git a/docs/UPGRADING-4.4 b/docs/UPGRADING-4.4
index 85f2aa2..d00c243 100644
--- a/docs/UPGRADING-4.4
+++ b/docs/UPGRADING-4.4
@@ -14,6 +14,12 @@ before you upgrade and look for changes to features you currently use.
 The support for C<jsmin> (via the C<$JSMinPath> configuration) has been
 removed in favor of a built-in solution.
 
+=item *
+
+You can separate configs in F<RT_SiteConfig.pm> into different files(with
+C<.pm> suffix) in F<RT_SiteConfig.d/> now, and they will have higher priority
+than original F<RT_SiteConfig.pm>.
+
 =back
 
 =cut
diff --git a/etc/RT_SiteConfig.d/Extension.pm b/etc/RT_SiteConfig.d/Extension.pm
new file mode 100644
index 0000000..d1352c5
--- /dev/null
+++ b/etc/RT_SiteConfig.d/Extension.pm
@@ -0,0 +1,4 @@
+# Plugin( "RT::Extension::QuickDelete" );
+# Plugin( "RT::Extension::CommandByMail" );
+
+1;
diff --git a/etc/RT_SiteConfig.pm b/etc/RT_SiteConfig.pm
index 683f2b7..cd68ad9 100755
--- a/etc/RT_SiteConfig.pm
+++ b/etc/RT_SiteConfig.pm
@@ -15,6 +15,9 @@
 #   perl -c /path/to/your/etc/RT_SiteConfig.pm
 #
 # You must restart your webserver after making changes to this file.
+#
+# If you have a lot to config here, you can also separate them into
+# different files in RT_SiteConfig.d
 
 Set( $rtname, 'example.com');
 
diff --git a/lib/RT/Config.pm b/lib/RT/Config.pm
index 5253d45..ce7c8ab 100644
--- a/lib/RT/Config.pm
+++ b/lib/RT/Config.pm
@@ -88,6 +88,10 @@ Second file is F<RT_SiteConfig.pm> - site config file. You can use it
 to customize your RT instance. In this file you can override any option
 listed in core config file.
 
+If you have a lot of things to config, you can separate them into different
+files(with C<.pm> suffix) in F<RT_SiteConfig.d/> directory, and they will
+override settings in F<RT_SiteConfig.pm>.
+
 RT extensions could also provide their config files. Extensions should
 use F<< <NAME>_Config.pm >> and F<< <NAME>_SiteConfig.pm >> names for
 config files, where <NAME> is extension name.

-----------------------------------------------------------------------