That sounds like it could work. Thanks for all the help everyone,
I've always managed to get good advice here with only the minimum of
uncessesary forum attitude that is often found elsewhere!! These
suggestions will definately set me on the path to getting a better
setup for my purposes.
Cheers!
On Jun 27, 5:59 pm, francky06l <[EMAIL PROTECTED]> wrote:
> Not much choice of having a separate webroot per config. You do not
> need a switch if in your index.php you define a value such as
> define('DBCONFIG', 'config1'), etc ..
>
> Then in your databse.php you can have multiple dbconfig having the
> name of the define. In app_model you can set $var $dbConfig =
> DBCONFIG.
>
> Of course you would have to update your css in each webroot (also img
> etc ..)
>
> On Jun 27, 4:50 pm, "Jonathan Langevin" <[EMAIL PROTECTED]> wrote:
>
> > btw, each webroot's index.php would need to be configured to know the cake
> > core and app install locations
>
> > On 6/27/07, Jonathan Langevin <[EMAIL PROTECTED]> wrote:
>
> > > if i were you, i'd check into the possibility of upgrading
>
> > > in the meantime, cake core already has the ability to be located
> > > elsewhere, as does the app folder, so your only true issue is using a
> > > different db config per site
>
> > > what I would do, is put your entire cms in a central accessible location,
> > > then copy your app/webroot into each website folder. modify the webroot's
> > > index.php to hold a $site_id value, assign a value in each site's
> > > index.php
>
> > > then in the database conf file, setup a switch based on the $site_id
>
> > > if you need more help, lemme know
>
> > > On 6/27/07, quincy < [EMAIL PROTECTED]> wrote:
>
> > > > I apologise in advance becasue I know this has come up many times
> > > > already, but I cannot seem to find the information I'm after. I want
> > > > to be able to have a single installation of my cake app (a CMS) on a
> > > > server, and run several sites from the same installation by simply
> > > > using a different database config file on each one. The only other
> > > > thing that might change would be CSS files so that each client can
> > > > have a customized colours or logos etc, but the point is that I want a
> > > > single point of upgrade for the CMS so that when we reach a new
> > > > version it can propogate across every site that uses it.
>
> > > > To put it another way, one set of models, views and controllers, and
> > > > many sites running off this one application by simple specifying the
> > > > relevant DB config file and maybe stylesheets. Thats it.
>
> > > > Any help greatly appreciated. I am using quite an old version of cake
> > > > as upgrades have not been possible during the development of our CMS
> > > > (long story), the version according to the config is 1.1.14.4797
>
> > > > Cheers
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
