Ah yes.  Missed that small part about the shared public directory.  Just thinking out loud.

On Fri, Sep 28, 2012 at 1:18 PM, Demian Katz <demian.katz@villanova.edu> wrote:
The problem is that there is only one public directory -- all the instances share the same public/index.php; we just load different configuration files based on environment variables set up by Apache... and it's the conditional setting of these variables that is failing in the current configuration.

As I just mentioned in a follow-up to my original message, I did discover a workaround that, similar to your suggestion, relies on having a different public directory for each instance (or, at least, simulating different directories by using symbolic links).  I really don't like it much, but at least it offers some kind of solution.

Now if we can find a solution that a) doesn't create duplicate stuff in the file system and b) can be easily automated through install.php in a cross-platform way, I'll be really happy.  But at least I can rest easy that Monday's beta release can be made to work in a multisite configuration, even if it's not especially pretty.  For a beta, that's good enough... but we should improve this before the true 2.0 release.

- Demian


From: John Wynstra [john.wynstra@uni.edu]
Sent: Friday, September 28, 2012 2:06 PM
To: Demian Katz
Cc: vufind-tech@lists.sourceforge.net
Subject: Re: [VuFind-Tech] VF2 multiple configurations: need Apache expert advice

Just a thought. If I am understanding this correctly,  what about moving the directory based configurations over to a .htaccess file in the respective directories instances.  Things like the rewrite rules and rewrite base directives?

Disclaimer - I don't claim to be an Apache expert.

On Fri, Sep 28, 2012 at 11:58 AM, Demian Katz <demian.katz@villanova.edu> wrote:
I've been testing and documenting VuFind 2.0's multisite capabilities -- the fact that you can set up multiple configurations for a single instance of VuFind -- and am running into some unexpected problems.

There are ideally two ways to do this -- host-based (site1.vufind.org, site2.vufind.org, etc.) or directory-based configuration (vufind.org/site1, vufind.org/site2, etc.).

I thought the host-based configuration would be the hard part, but that seems to work quite nicely.

I'm having trouble with the directory-based configuration, however.  It appears that if you load multiple instances of VuFind's default httpd-vufind.conf file, the RewriteBase directives conflict with one another, and only the last-loaded configuration works properly.  I've been banging my head against this all day and can't find a good solution.  It probably requires reinventing the mod_rewrite configuration.  I don't want to make the default configuration incredibly complicated just to satisfy this one edge case.

Any brilliant ideas?  You can learn more about the current state of the art here:

http://vufind.org/wiki/vufind2:installing_multiple_instances

thanks,
Demian

------------------------------------------------------------------------------
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Vufind-tech mailing list
Vufind-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vufind-tech




--
<><><><><><><><><><><><><><><><><><><>
John Wynstra
Library Information Systems Specialist
Rod Library
University of Northern Iowa
Cedar Falls, IA  50613
wynstra@uni.edu
(319)273-6399
<><><><><><><><><><><><><><><><><><><> 




--
<><><><><><><><><><><><><><><><><><><>
John Wynstra
Library Information Systems Specialist
Rod Library
University of Northern Iowa
Cedar Falls, IA  50613
wynstra@uni.edu
(319)273-6399
<><><><><><><><><><><><><><><><><><><>