On 23.06.2011, at 09:52, 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?
We have doen projects with multiple applications in one git repo in projects. The idea being that for development its easier to have them all in one repo, but for deploying we want to keep them separate. For example one server with the admin interface, another one with the frontend, another one with the API. this lets us scale things separately. it also makes it easier to control the impact of misconfigurations etc. We have defined a dir structure for this and also developed tools to handle packaging the applications into separate .deb files: https://github.com/liip/sf2debpkg regards, Lukas Kahwe Smith [email protected] -- 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
