Allow parallel letodms instances sharing one source

[steinm]

I'm about to use letodms for a customer and probably not just one but many. In order to separate them propperly I have to install letodms for each customer.

How about sharing at least the source in a way typo3 is doing it. That means to have a central installation of letodms and various instances (directories somewhere below DOCUMENT_ROOT) which have just links to op, out, inc, styles. This is almost feasable right now, if inc.Settings.php
was moved out into an extra directory in each instance. This way each customer would have its own configuration specifying its own database and content directory.

Uwe

[matteo lucarelli]

on a *nix system you can use the hard-link for obtain that.

Elsewhere you should simply link in the code different settings file (and then different DB/Data folders) for every user.
The modification should not be difficoult (if you're a PHP developer) at least a bit time consuming (because settings.inc is included everywhere) but I've never tried.

The best way should be substitute settings.inc with a function able to select the right one.

Some other issues can emarge by the autentication mechanism.

Let us know

[steinm]

hard-links are an option but something I only use as a last resort. In this case the settings.inc
seems to be the bigger problem. I don't like to change any file including settings.php and losing the ability to upgrade to newer version of letodms easily. I hoped we could find a solution by changing the official source of letodms. I wouldn't mind to make a patch.

[Reinhard_G]

Hello, Uwe (steinm),

I would try this:

• copy all LetoDMS-Files into a central folder
  
• create for each configuration the scripts index.php and inc.settings.php
  
• Each configuration needs also a data folder.
  
• Create for each configuration a database and create the db content (create_tables.sql)
  

Review and change, if neccessary, all path- and all db-settings in these two files. This should work. Good luck.

Reinhard

[steinm]

I can't see how this solves the problem with including inc.Settings.php in almost all other php scripts. Having several inc.Settings.php files is just part of the solution. They need to be put somewhere and that should not be the inc directory. Just changing the path to inc.Settings.php in index.php isn't sufficient.

[matteo lucarelli]

We're working on a definitive solution. It will be included in the next release.

---

We're working on a definitive solution. Will be applied in the next release.