I have to agree with Adam on this point. The whole concept of admin routing is to provide radically different interaction capabilities and layouts separated by end users and administrators.
Duplicating code in two separate apps is poor practice. Think about scalability and enhancements. Why maintain twice as much code as you need to? As for security, I don't understand what advantage 2 apps give you.. especially since they will most likely share the same host and file system anyhow. If anything it just means more work to test and eliminate security issues that may result from the code. On Dec 10, 11:08 am, Adam Royle <[EMAIL PROTECTED]> wrote: > What security reasons are you talking about in particular?? It doesn't > make sense to break it into two separate apps when they share > everything. > > On Dec 10, 1:11 am, Marieta Nastase <[EMAIL PROTECTED]> wrote: > > > I have the same problem!! > > > What is the best way to deal with this? > > > In my opinion, 2 separate applications is the best solution, for > > security reasons. But the webroot is the problem(files uploaded are > > needed both in backend and frontend app). > > > Marieta > > > On Nov 7, 10:50 am, Kappa <[EMAIL PROTECTED]> wrote: > > > > I agree with you, but at the same time i think that having separate > > > webroot for admin and public app is quite hard, because often the > > > admin > > > app is used not oly to insert "written" data but also to upload > > > images, > > > videos,files and so on.. and i suppose that all those data have to be > > > put > > > inside a "common" webroot. > > > > Am I right? > > > > Andrea > > > > PS: i think that the Admin/Public implementation on the CakePHP > > > framework > > > is one of the trivial things, because there is not "THE WAY" to do > > > it, > > > but everybody find himself creating its own way. I hope that in Cake > > > 1.3 > > > or 1.4 the Cake team will develop a standard way for doing it. > > > > On Nov 7, 1:54 am,AdamRoyle<[EMAIL PROTECTED]> wrote: > > > > > If you're sharing the same webroot and models, controllers, > > > > components, etc, what is the purpose of have two separate apps? > > > > > You can just use admin routes for this. > > > > > Cheers, > > > >Adam > > > > > On Nov 7, 5:55 am, WildFoxMedia <[EMAIL PROTECTED]> wrote: > > > > > > I saw an article on the bakery that described a method for creating 2 > > > > > seperate applications that could share Models, Controllers, > > > > > COmponents, etc. > > > > > I followed that tutorial and had everything setup how I wanted, > > > > > except for > > > > > the webroot. Is it possible to share the webroots across these 2 apps? > > > > > > I thought about removing everything from the webroot for each app > > > > > except for > > > > > the index.php for that sake of bootstrapping and actually dispatching > > > > > the > > > > > request - but moving the rest of the files to a shared webroot in a > > > > > similar > > > > > fashion to the models, etc. My question is this.... > > > > > > Is it easy, or even possible to change system paths for Forms, JS, > > > > > CSS, etc. > > > > > to reference a new shared webroot, or at worst, make the public app > > > > > have all > > > > > webroot files and the manager leach its files? > > > > > -- > > > > > View this message in > > > > > context:http://www.nabble.com/Seperate-Public-Admin-Apps-with-Shared-Models--... > > > > > Sent from the CakePHP mailing list archive at Nabble.com. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
