In trying to structure our website using three apps and various bundles, we’ve run into a major architectural fork in the road which nobody seems to have the right answer for. I’ll try and paint the picture as clearly and quickly as possible:
Assume 3 applications: Frontend, Backend, and Api Assume an ArticleBundle for the purposes of creating articles on the website Assume that all 3 of the above apps will use articles in some way, you’ll create and view them in the frontend, you’ll have administration tools for them in the backend, and you can retrieve them via the api. Here are the options as we see it: a) Our ArticleBundle only has Document(s) and Form(s) but no controllers, and we move all the controllers and routing to the Application level, so FrontendBundle might have an ArticleController. b) Use four separate Article bundles, FrontendArticleBundle, BackendArticleBundle, ApiArticleBundle, and CommonArticleBundle. The first three bundles would extend CommonArticleBundle. The Frontend app would then only use the FrontendArticleBundle, backend app uses BackendArticleBundle, etc. c) Use one ArticleBundle with 4 controllers within it, FrontendController, BackendController, ApiController, and CommonController, the first three extending CommonController. Each app would use the ArticleBundle but would only route to the specific controllers it needs. Option b seems to be most in line with the idea that bundles are stand alone entities. thoughts anyone? Jay -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
