[jira] Resolved: (SHINDIG-395) Local configuration file and extension class path

["Chris Chabot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SHINDIG-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Chabot resolved SHINDIG-395.
----------------------------------

    Resolution: Fixed
      Assignee: Chris Chabot

Something to this effect has been committed a while ago, was a good idea indeed!

Config is now in shindig/php/config/container.php, and local.php is included if it exists

> Local configuration file and extension class path
> -------------------------------------------------
>
>                 Key: SHINDIG-395
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-395
>             Project: Shindig
>          Issue Type: New Feature
>          Components: Common Components (PHP)
>         Environment: n/a
>            Reporter: Karsten Beyer
>            Assignee: Chris Chabot
>            Priority: Minor
>         Attachments: fix-issue-SHINDIG-395.patch
>
>
> There should be a possibility to store local configuration values outside of svn control. The attached patch includes a local.config.php if it exists in which configuration values can be overwritten.
> Additionally in order to keep the container specific handlers and other classes cleanly separated from the shindig project, it should be possible to add paths in which classes are searched for. This is implemented by adding the "extension_class_paths" parameter which should be an array of paths which is then used in the __autoload function to search for extension classes.
> Patch will be attached immediately...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.