Re: Backend best option

> we usually do two full installs of cake so that things are fully separated

Don't understand why you'd want two copies of your code.
What is it that has you so worried, you are bending over backwards to
protect?

> The biggest benefit in my opinion, though is that you can work on
> admin functionality without having to worry so much about touching/
> bringing down the public site.

Can't you still do that given that the admin actions are all
different?

If you are changing shared code, you still have to worry about
bringing down the front end when you eventually synch up the back and
front end copies of your shared code.

Honestly, not sure what the gain is to the two separate system copies.
If the code was totally different, I guess I can see benefit . But
surely you are sharing lots of code between the two.

I have a single code base with a separate admin plugin that handles
the admin section. But it draws on lots of shared code.

Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.

You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en