Due to the reasons explained by WebbedIT, the best thing to do is just use admin routing. At the minimum, the models used by your admin and end-user "apps" are going to be nearly identical, if not the behaviors/ views/elements/helper/controllers/components as well. So it just doesn't make sense building two separate applications, especially when Cake makes it so easy to build a separate admin area with Auth and admin routing.
On May 19, 3:55 am, WebbedIT <[email protected]> wrote: > I am currently developing a large app which needed an area for the > site owner to administrate the site, another area for organisations to > administer their content and an area for standard site users to > register and maintain their profiles. > > At first I thought it was sensible to do 3 apps on seperate sub- > domains but you soon realise that you end up duplicating a lot of code > and when you make a structural or cosmetic change it becomes a lot > more work to replicate it across the 3 sites. Didn;t take me too long > to integrate all 3 sites into the one app and it's so much better now. > > My vote, use routing or whatever other method you want but keep it all > in the same app. > > HTH > > Paul. > > Check out the new CakePHP Questions sitehttp://cakeqs.organd 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 [email protected] > To unsubscribe from this group, send email to > [email protected] For more options, visit this group > athttp://groups.google.com/group/cake-php?hl=en 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 [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
