RE: [Phpwebsite-developers] PHPlib & Multiple Instances

[Geoff S. <Ge...@Ho...>]

Todd:

What I plan to do is Install the software on one domain and the database on
a separate domain. Or, I will install multiple copies of the software in
separate directories on the same domain. So, that would involve complete
installs of the software (including the config file) for each "instance".

I suppose that I could run multiple instances through the same copy of the
software installed in a single location. But, I want to be able to customize
each instance if I choose to. I haven't played with the software
sufficiently to determine the extent to which I could customize with a
single installation of the software.

BTW: I have a question about CVS. I haven't used CVS before, so...

I found a reference to SSH and downloaded it from ssh.com. But, I can't get
it to login as anonymous and I don't have my CVS access yet. Can you tell me
what I need to do to at least gain anonymous access?

Thanks,

Geoff

-----Original Message-----
From: php...@li...
[mailto:php...@li...]On Behalf Of
Todd Owen
Sent: Saturday, March 24, 2001 9:55 PM
To: php...@li...
Subject: Re: [Phpwebsite-developers] PHPlib & Multiple Instances


Geoff, your logic looks good to me.  I assume $dbp means "database
prefix". My only question is how will $dbp be assigned?  Will there be
separate config files hard coded for each site?

BTW, I don't have anything left to commit; you might check on Matt's
calendar rewrite though.

As I was writing up my long range goals, I ran across the opposite problem
that Geoff had.  What if your site(s) get too large for one database server
to handle?  Let's assume you're using the one table approach and you have
100,000 users and 1,000 sites on a single install.  I can forsee the
threaded discussion groups and mailing list archives for these organizations
growing VERY quickly.  I think we need to code with this in mind.

I'm thinking about a server for core features and most plug-ins, but a
separate database server for forums and list archives and possible a third
for images (although not in a database).  This can be solved by connecting
to separate database servers once and passing the database handler to the
appropriate objects in a similar way Geoff proposed abstracting the table
name.  Thoughts anyone, anyone?

--Todd



_______________________________________________
Phpwebsite-developers mailing list
Php...@li...
http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers