As it stands now, I'm developing two services, deployed on the same server, sharing the same database. These services each have different hostnames. I have 3 bundles, one for each service and a shared bundle with the entities.
If I have one application i have to seperate the services with routes, and that is not possible. I have to seperate them by hostname. And that is why I chose to create two application. If there is any way to avoid this then I'm happy to oblige, but at the moment this is the situation. On 23 Juni, 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
