[
https://issues.apache.org/jira/browse/SHINDIG-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680172#action_12680172
]
Brent Theisen commented on SHINDIG-927:
---------------------------------------
Thanks Chris but that doesn't really work for me. I've got about ten people
who need to run shindig locally, half of which are designers and strictly HTML
types who would need me to tell them every time they need to copy a change to
local.php in to the shindig external part of their working copy.
Guess I'll just commit the shindig codebase in to my own repo.
> Check for existence of config/local.php in include path
> -------------------------------------------------------
>
> Key: SHINDIG-927
> URL: https://issues.apache.org/jira/browse/SHINDIG-927
> Project: Shindig
> Issue Type: Improvement
> Components: PHP
> Affects Versions: trunk
> Environment: CentOS
> Reporter: Brent Theisen
> Priority: Trivial
> Fix For: trunk
>
> Attachments: fix-927-bug.patch
>
> Original Estimate: 0.02h
> Remaining Estimate: 0.02h
>
> I'm using an svn external to deploy shindig on production Linux servers as
> well as our development team's MacBooks. So, I need a config/local.php for
> both production and our local development environment. That way, I can have
> compress_javascript off and debug on when I'm developing locally but still
> have the correct setup in production.
> The directory structure and config files are like so:
> htdocs/shindig/ (svn:externals property set to shindig trunk)
> htdocs/shindig_configs/local/config/local.php
> htdocs/shindig_configs/prod/config/local.php
> Then for the Apache httpd.conf for prod I set the include path to something
> like "htdocs/shindig_configs/prod:.:/htdocs/shindig". For the local
> development httpd.conf I have the same include path directive except the
> first path is htdocs/shindig_configs/local.
> But this doesn't work until changing the file_exists() call in Config.php to
> a fopen() that looks for the file in the include path. I'm including the
> patch I'm using in the hopes you guys might commit it. Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
