It depends on your situation and needs. I'm using admin routing in one application, as it's very simple. In another application, I'm actually creating an administration backend (currently) on an entirely different user account on the same server (Dreamhost users' are unable to access other users' files). Eventually I'll move it under the same user, it's currently separate because I've been unable to figure out a test case to prove a bug with the Cake core. Regardless, it will remain its own entity and never use admin routing.
To clarify, I'm not doing the separation because of simplifying the organization of application directories. I'm doing it because the admin side of things will also act as a portal for staff, so there will be more than just administration of the main website on that side of things. On Apr 21, 4:18 pm, adam <[email protected]> wrote: > When you create an admin backend, do you create it as its own > application that uses the same db, or do you create it all in one > application? > > Just curious. I know admin routing is powerful, but didn't know if > people opted to separate the applications to simplify the organization > of application directories. > > Adam --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
