Thank you guys for the answers! So the reasons why I want to have two apps instead of one are:
* It's easier to maintain one app without running the risk of "damaging" the other one. * Reusability * What if I only want ONE of the two apps? On the other hand I want the apps to access the same data ... ok, no problem with the database, but what about the filesystem? I found a nice article in the bakery, which helps me out quite a lot: http://bakery.cakephp.org/articles/view/141 So here my directory structure could be: - cake - apps - site - cms - www - site - cms Of course only the www-part is public, I can access the apps through "www.mydomain.com/site" and "www.mydomain.com/cms". "site" and "cms" are the WEBROOT_DIRs of the corresponding applications. I think this could work for me, now I have to solve the problem of routing and url-"clearance", but that's another problem! :-) Thank you, Christoph On 4 Feb., 13:21, "Sam Sherlock" <[EMAIL PROTECTED]> wrote: > It does sound like this is going to have some draw backs; > > - double work load > - lack the automagic that makes cake so sweet > - its to installations of cake to upgrade > - and once completed is either going to require > - administrative procedures of copying files > - a great deal of bespoke customisation to the server (perhaps > aliasing the image folder) > > either way it sounds like a lot of work; I see the appeal of having separate > admin/public sections to the site but not when using cake. > > On 04/02/07, Kaste <[EMAIL PROTECTED]> wrote: > > > > > hm, no help on this topic so we might not know, what the real problem is. > > > > How do you guys implement multiple apps e.g. website + cms? How does > > > your directory structure look like? What about your routing? How do > > > you implement the content sharing between the apps? > > > > I had the idea to make two single apps - one for the website, one for > > > administration & content management. The website is available at > > > mydomain.com, the CMS at cms.mydomain.com. Both apps have their own > > > models, controllers, etc. but they should share the same content > > > directory, which holds uploaded files like images, videos, and so on. > > why do you split one "thing" into two apps. > > "where" is the content? you can connect to the same db/tables from your > > apps. > > why do the admin and the public/user section of your site have different > > models? different views, of course, different controller, yep. > > > you want to "share" the webroot? but: <a href="towhateveryoulike"></a>, > > same with <img>. > > of course you cant link to anything outside your htdocs, so put everything > > in the cms-webroot (obfuscating there is a admin-section) and copy/move > > the uploaded files accordingly. > > > but: since you seperated them, and presuming this was the right decision > > for your domain, dont couple them afterwards. just do what you would do > > with flickr for instance. ("api-calls") > > (you dont share anything between diff apps without an interface) > > > but eventually i have no idea of what the problem is ;-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
