It looks like you could get the job done using plugins.
They were designed to do pretty much what you want. They are their own
little apps inside the app but they share all the layouts, css images
and things from the main application. You can use global things like
authentication from the main
I would take a cake dir per application and not share anything
amoungst them.
If you would update cake, and something is wrong, all your apps go
wrong.
On 11 mei, 00:32, Dave [EMAIL PROTECTED] wrote:
Hi All,
I've been thinking about using Cake as a framwork for the company
intranet, but am
On Sun, May 11, 2008 at 3:57 AM, woldhekkie [EMAIL PROTECTED] wrote:
I would take a cake dir per application and not share anything
amoungst them.
If you would update cake, and something is wrong, all your apps go
wrong.
I think the opposite would be a maintenance nightmare. If an
You could store the specific models and controllers in a subfolder
like so:
app
__controllers
sales
finance
__models
sales
finance
Cake will find controllers automaticly, but I thought this doesn't on
views like this
On 11 mei, 00:32, Dave [EMAIL PROTECTED] wrote:
Hi All,
There is going to be a hardcore test environment before anything goes
live, so hopefully when updating libraries nothing would go wrong.
Plus one cake dir per application would still require layouts and
common components to be copied into each one, creating it's own
maintenance nightmare, no?
On
Hi All,
I've been thinking about using Cake as a framwork for the company
intranet, but am coming unstuck as how to share the libraries and
structure things.
The Intranet is made up of two parts, a portal like homepage, and a
potentially infinite number of applications running in it, each in
