Ah, no I think you misunderstood; I meant the version roll-out of the
shared app not the cake libs, the app itself would be updated far more
frequently then the cake.
As you say, ofcourse, you dont want to give users the ability to make
modifications to the app, however, I can think of more then a
On Sun, Apr 17, 2011 at 7:37 AM, Yuka Poppe wrote:
> Hi List, Cricket,
>
> How would version rollout work? With a single codebase, and thus a
> relatively userbase, the project gets big quickly. Customers request
> different features, you'll look at all the feature requests and will
> decide to im
Hi List, Cricket,
How would version rollout work? With a single codebase, and thus a
relatively userbase, the project gets big quickly. Customers request
different features, you'll look at all the feature requests and will
decide to implement a few that make sense to the whole lot.
There comes a
On Sat, Apr 16, 2011 at 10:32 PM, Yuka Poppe wrote:
>
> Yep, you're absolutely right about automation, that wasnt a very solid
> point. Symlinks are nasty though -- if ony from your customers
> perspective -- they dont understand what it is and how it works. You
> cant serve those things to your c
On Sun, Apr 17, 2011 at 3:38 AM, cricket wrote:
> What you and Krissy said makes sense, and is what I had in mind. But
> it seems to me that there would be issues surrounding AppController ad
> sessions. Maybe not. I haven't put too much thought into it.
Hmm, I hadn't even thought about sessions
On Sat, Apr 16, 2011 at 7:02 PM, Yuka Poppe wrote:
> The location of document root (app/webroot/ in CakePHP land) is
> variable. One can put the entire app in a directory accessible by each
> vhost/webserver/what-have-you, and also make sure its somewhere that
> can be seen by php.
>
> Have the we
The location of document root (app/webroot/ in CakePHP land) is
variable. One can put the entire app in a directory accessible by each
vhost/webserver/what-have-you, and also make sure its somewhere that
can be seen by php.
Have the webserver serve up any request that isnt a static file by the
'sh
ion was if it's possible
to do with cake.
No? Did I read it wrong?
K
-Original Message-
From: cake-php@googlegroups.com [mailto:cake-php@googlegroups.com] On Behalf
Of cricket
Sent: Saturday, April 16, 2011 7:19 PM
To: cake-php@googlegroups.com
Subject: Re: Cake PHP as Multisite /
On Sat, Apr 16, 2011 at 3:28 PM, Vitor Pacheco wrote:
> you can configure additional folders for your classes in bootstrap.php
> http://book.cakephp.org/view/916/Additional-Class-Paths
Good point. That would be better.
Whether the original idea is a good one, though ...
--
Our newest site for
you can configure additional folders for your classes in bootstrap.php
http://book.cakephp.org/view/916/Additional-Class-Paths
2011/4/16 cricket
> On Sat, Apr 16, 2011 at 2:40 PM, cricket wrote:
> > On Sat, Apr 16, 2011 at 2:37 PM, Carlos Eduardo Sotelo Pinto
> > wrote:
> >> Thanks Cricket
> >
On Sat, Apr 16, 2011 at 2:40 PM, cricket wrote:
> On Sat, Apr 16, 2011 at 2:37 PM, Carlos Eduardo Sotelo Pinto
> wrote:
>> Thanks Cricket
>>
>> Well that is not the point or target that I am looking for, I am
>> looking for share the complete app, and having diferents webroot, I
>> mean shareing
On Sat, Apr 16, 2011 at 2:37 PM, Carlos Eduardo Sotelo Pinto
wrote:
> Thanks Cricket
>
> Well that is not the point or target that I am looking for, I am
> looking for share the complete app, and having diferents webroot, I
> mean shareing the app and having one approot foreach domain with its
> o
Thanks Cricket
Well that is not the point or target that I am looking for, I am
looking for share the complete app, and having diferents webroot, I
mean shareing the app and having one approot foreach domain with its
own database. I am think on a server with a cakelib and app installed,
and the us
On Fri, Apr 15, 2011 at 8:07 PM, Carlos Eduardo Sotelo Pinto
wrote:
> Hi people.
>
> I have read this article and thinking on a new challenge ( if it coudl
> be called a challenge ). What about having a cakephp installed on a
> server.. like a dedicated server, optimized for multiple domains, for
14 matches
Mail list logo
