I am using 2 applications in my sf2 project. One is holding frontend configuration and second is for backend configuration. We decided to use 2 applications because both configs are way different but use same databases, same entities and some common bundles. When we separated backend and frontend applications then we have only whats really needed in project container.
On 23 Cze, 12:36, Fabien Potencier <fabien.potenc...@symfony- project.com> wrote: > On 6/23/11 9:52 AM, Robert Knutsson wrote: > > > > > > > > > > > Hi > > > I needed two applications in my symfony2 project and read the manual > > (http://symfony.com/doc/2.0/cookbook/symfony1.html) where > > the concept of applications in symfony2 was explained. > > > Although the manual is very vague on how to implement two > > applications, and there is no "best-practice" to be found on the > > subject. > > > My issue is that I wanna keep duplicated code to a minimum, and I need > > some input on how to not duplicate "bootstrap.php.cache", > > "autoload.php" and "console". > > > Could you recommend me some best practices when it comes to multiple > > applications in symfony2 or share your experiences? > > Short answer: You never need more than one application in Symfony2. > > Can you explain why you want to create two applications? > > Fabien > > > > > > > > > Cheers, > > Robert -- 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 developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
