NYCPHP Meetup

Fri Dec 12 08:11:55 EST 2008

That's the best way so each DB is unique, easier to manage and less
resources used.
Using a db as single sign on means then you have to use one master db
then use table prefixes to keep each site unique. Its way too early in
the morning to think about how this would impact session id's etc.Also
if the sites are physically remote from each other now you have to
authenticate across the internet versus locally.
HTTPS would be fun...  heh

oz
On Fri, Dec 12, 2008 at 5:01 AM, David A. Roth <davidalanroth at gmail.com> wrote:
> The intention here is not to share the Joomla database with another
> instance, but to keep them separate. If the MySQL database created has its
> own name to match the instance, then this would prevent each instance from
> interfering with another which is the objective. The purpose is to have
> these instances behave as if they were on totally different machines with no
> relationship to each other. Here is a detailed example:
> www.example.com/website1 with a Joomla directory name of website1 using a
> MySQL database name of website1_db, website1_usr for the MySQL account to
> access it, with a table name of ws1_ (instead of jos_).
> www.example.com/website2 with a Joomla directory name of website2 using a
> MySQL database name of website2_db, website1_usr for the MySQL account to
> access it, with a table name of ws2_ (instead of jos_).
> Creating a different table name for each instance so there is no mistake in
> what is being referred to.
> The above is how I have been doing this where I have several instances of
> Joomla on the development server so I can keep a demo instance, development
> instance and a staging instance. I then use the Joomla backup component,
> JoomlaPack, to easily move an instance to another server.
> You have given me an idea. If someone has several related Joomla instances
> where there was a need to share the user registrations amongst them, then
> what you are suggesting would be useful, although I've not done that myself
> yet.
> David
> On Thu, Dec 11, 2008 at 10:21 PM, <masimko at verizon.net> wrote:
>>
>> T
>> MIME-Version: 1.0
>> Content-Type: text/html; charset=UTF-8
>> Content-Transfer-Encoding: 7bit
>> X-Originating-IP: [208.54.90.35]
>>
>> <html><head>
>>
>> <link media="all" type="text/css"
>> href="/webmail/static/deg/css/wysiwyg-4096788580.css" rel="stylesheet">
>> </head><body>
>> <br>Joomla is self-contained within the directory it is installed. The
>> only<br>external requirement is the MySQL database which simply needs to
>> have a<br>different name for each Joomla installation to keep them totally
>> separate.<br><br>Not entirely accurate. Joomla sites can share a database if
>> the table prefixes are different.<br><br>The default prefix is jos_. If you
>> are sharing the mysql database with another instance of Joomla!,<br>set the
>> prefix to something other than the default in the installation
>> dialog.<br><br>I've put Joomla below the top level in one website during
>> testing and transition, and set the home<br>menu link to point up one level
>> in the directory structure out of the Joomla! system.<br><br>I've also put
>> SugarCRM and phpGroupware below Joomla! in the directory structure, but
>> without trying<br>to link to them from the Joomla! menu.<br></body></html&gt
>> ;
>
> _______________________________________________
> New York PHP SIG: Joomla! Mailing List
> http://lists.nyphp.org/mailman/listinfo/joomla
>
> NYPHPCon 2006 Presentations Online
> http://www.nyphpcon.com
>
> Show Your Participation in New York PHP
> http://www.nyphp.org/show_participation.php
>

NYCPHP Meetup

NYPHP.org

[joomla] Two Joomla sites on one hosting package?