From: Jason C. <cam...@xp...> - 2001-04-17 10:53:32
|
I like this idea too. I thought this was how we were going to do the administrative engine but I could be wrong. As for one database having multiple sites in it, I'm all for that for the people that want it. I just don't see why a big ISP would want say 40 customer sites in one database. I know I won't be doing that for my customers. Everyone is having a separate database because I think its safer that way in the long run. What happens if someone corrupts their database for some reason? That could corrupt all the tables for all the sites in some way. Also, having them all have their own login/pw for each table of theirs in the database is a pain to have to do compared to just assigning a login/pw to a database. I'm just not on the "go" side for having multiple sites in the same database as you can tell :) Someone make me a believer of this concept because I see no point in it. If I had a customer that wanted to run two phpWebSite installations then I'd give them another database /w login/pw for that site as well. I wouldn't include the first and second site in the same database. Anyways, thats my thoughts on it..... > 2. About the permissions problem you were referring to (one or two 'r' > here? I can have it wrong, I'm a Luxembourger). I really like the > Windows NT/2000 platform :). And what I most like about it, is the very > powerful and flexible permissions system. Can't we somehow do something > along those lines for phpWebSite? That would mean to have users, groups > that users can belong to, and "user and group roles". For instance: in > order to post a news item, you need to have the "news editor role". If > the user alain either has the "news editor role", or is member of a > group having the "news editor role", he can post a piece of news. That > wouold be very flexible actually. > > Thanks for reading ! > Jason Campbell Xplozive Media Technologies www.xplozivemedia.com phpWebSite Developer |