[Owncloud] Multiple Instances on one server

[Arman Khalatyan]

Hi,
I think making more complex config file will make headache for setup. It
will affect on performance if we  push routing tasks to OC framework.
In tems or performace one need to keep things as simple as possible and
separated.
I will advise  to separate multiple websites by webserver (apache or what
ever) suggested by Christian. It gives almost zero overhead.

Cheers Arman.
On Feb 15, 2013 10:32 AM, "Christian Reiner" <foss at christian-reiner.info>
wrote:

> Hi,
>
> On Friday 15 February 2013 10:07:03 Jörn Friedrich Dreyer wrote:
> > I could upstream some code I wrote for a customer that reads an
> environment
> > variable to determine which config to read. If it is set to 'test'
> > .../config.php will become .../config.test.php
>
> independant of the question if such strategy makes sense at all:
>
> wouldn't it be better to keep that logic inside the config file? As to have
> more than a single config section in there and simply switch between them
> by
> evaluating an environment variable? The default branch could point to one
> instance or an error (both makes sense). And one could still include
> different
> files from there if that design appears more modular.
> The advantage of keeing the switch inside the config file is that it
> reduces
> confusion about why suddenly the changes I made in the config file don't
> apply. It keeps configuration at a single place.
>
> Cust my 2 cents...
>
> --
> Christian Reiner (arkascha)
> [ foss at christian-reiner.info ]
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/owncloud/attachments/20130218/33c1975e/attachment.html>