Re: [VuFind-Tech] One vufind core serving multiple libraries

[Demian K. <dem...@vi...>]

Sorry for not getting back to you sooner – the holiday break email pile-up was pretty bad!

In any case, as I noted in my previous message, Benjamin Mosior’s situation is probably the most similar to yours that I am aware of. If you still have specific technical questions that you need resolved, let me know and I’ll be happy to make some suggestions.

- Demian

From: it...@gm... [mailto:it...@gm...]
Sent: Monday, December 23, 2013 11:22 AM
To: vuf...@li...
Subject: [VuFind-Tech] One vufind core serving multiple libraries

We are planning to have installed multiple libraries on the same server.
And we want to have only one vufind-core, as you may guess.

The challenge is to have the seven vufind modules
module/VuFind
module/VuFindConsole
module/VuFindDevTools
module/VuFindHttp
module/VuFindLocalTemplate
module/VuFindSearch
module/VuFindTheme
located ouside of each library directory.

In other words we want the vufind-core on the same level as each library, for example:
/berlin-library/
/paris-library/
/vufind/module/VuFind/
/vufind/module/VuFindConsole/ .... and so on.

Obviously we are facing a large configuration task, involving many .ini, .conf and Module.php files.

Didi anyone went through similiar experience?
Where to start? What are the risks?
I tried to seach for relevant documentation, but did not find anything yet. Please let me know if there is any.

Thank you in advance for anything that helps.
Richard Urban