Could multiple installs of phpScheduleIt exist?

[gjb911169]

Is this possible to do?   I had posted in the Sourceforge forums re: adding tables.   Since I am not that knowledgable about MySql and php, I was looking to add multiple installations in order to have multiple categories.

Thanks.

Here is the original link from Sourceforge: http://sourceforge.net/forum/forum.php?thread_id=1440049&forum_id=331296

[Nick]

If you install them in different directories and use a different database name for each, it's no problem to have 2 distinct copies running.

[gjb911169]

Thanks for the help.  I have phpScheduleIt placed in my web server's root directory.  I am about to the add the tables into MySql via the install directory.   Where do I need to make the modification in order for the Database not to be overwritten?

Any help is appreciated.

Thanks
Greg

[Nick]

If you are using the web-based installer, change your config.php setting for $conf['db']['dbName'].

If you are using the manual installer, replace all 'phpScheduleIt' with a new name on lines 1-3

[gjb911169]

It worked well using the web install for the 2nd set.   Now I am trying to figure out to link the User information tables throughout the installs.   Is this best done through a change in MySql or is it a modification that needs to be done in a config piece during setup?

Thanks again for the assistance and the great product.

[Nick]

This is sort of supported right now.  Here's what you need to do:

In lib/DBEngine.class.php:

First, you need to add the name of the shared database to line 49, like this:

$this->dbs = array ($GLOBALS['conf']['db']['dbName'], 'shared_db_name');

Next, for the install that you want to point to the shared login, you need to add all of the table names in around line 106, following all the other's as an example.

'table_name' => $this->dbs[0]

Then, change the index of each table you want to grab from the shared db to 1.

Finally, comment line 119 and uncomment line 120.


This isn't a very slick solution because of all the weird data problems that can happen from this (a user is deleted, but reservations will still exist in the non-shared database).  A better solution would be to sync login data between the two databases.

[gjb911169]

Thanks.  I will take a shot with that and see what happens.