Security across multiple sites... Looking for solutions

Posted: Sun Jan 14, 2007 1:53 pm

Hello all,

As some here may well know, running multiple sites is difficult if your time is limited. Embarassed

I currently run a dedicated server and host various sites. I am sad to say I need to update all of them and yet. It is large task, I am seeing the benefit from keeping all installs (php-nuke) versions the same. So that when it is time to update, you just replicate the process for each site.

I am contemplating at the moment whether a central php-nuke install would be benificial to myself. Lets say I set up a skeleton for the php-nuke. All sites run from that but have, obviously, independant databases. Is this doable, is it practical, and what are some problems that may arise from doing so asid from theme modifications or custom modifications that you may only want on one site, and not another?

I suppose I could scrap the sites databases and start from scratch, there are some data/mysql databases that I would like to save. However trying to hand edit each database to piece it together after a meriad of different patches and upgrades sounds daunting Shocked

.

I will try to gather the Nuke Versions/PHPBB/NukeSentinel(tm) tonight and edit the the post to reflect my current status.

As always I am open to suggestions. I would really like to bring all these installs together and make a cohesive set of installs to make it easier to facilitate upgrades and patches. I would like to keep my sites safe, and generally my time on the PC is limited. If anyone else has had similar experience and would like to shed some light on how they have navigated through it, it would be nice to hear about!

Best regards,
Thomas

Posted: Mon Jan 15, 2007 3:07 am

Yes this is certainly doable. I do that myself Smile

What I do is set up Apache to change the DocumentRoot on those sites to the same path. Thus, one file set of phpNuke files. Then I can set up config.php to pick which database to use

The problems are indeed, different file customizations that you want to use. I don't do many customizations.. but theoretically you could have code that only runs for one site, and not on another. The same principle that config.php needs to pick the database, however I believe that would be such a hassle to maintain.
For themes, I don't see a way around it. Just don't allow users to select themes.

Really it depends on who needs access to the files. Since I'm generally the only one maintaining my sites, I know what is on there. But when different people start having access to the same files, then one person could easily ruin all the sites by changing a file.

My three main sites run on the same phpNuke fileset .. even the same users table. [ Only registered users can see links on this board! Get registered or login! ] [ Only registered users can see links on this board! Get registered or login! ] [ Only registered users can see links on this board! Get registered or login! ]
(Although there are limitations with the users .. esp where the forums come into play)

I find it pretty easy to maintain though, with few customizations, I can just patch them as needed without too much hassle.

Posted: Mon Jan 15, 2007 11:28 pm

evaders99, I am curious as to how you do this:

Quote:

I can set up config.php to pick which database to use

Since these are now all the same docroot. Are you checking the incoming URL string to know which db credentials to use?

Posted: Wed Jan 17, 2007 12:34 am

Using $_SERVER['HTTP_HOST'] to check Smile

Posted: Sun Jan 21, 2007 7:32 am

Ah, very easy. Thanks! Wink