On 08.12.2010, at 10:21, Lukas Kahwe Smith wrote: > Hi, > > We have decided to use multiple separate frontend controllers in our > application which will run on separate (sub)domains. For example this way we > can if the site overloads ensure access to the admin tool since we can easily > either have a dedicated server for the admintool or by disabling the > main/mobile front controllers for one physical server and direct all admin > traffic there. > > Right now we have one for the main site, one for the mobile site, one for all > static content (*) etc. This is all developed in one git repository and we > use a perl script which we wrote (and yes it will become OSS eventually) to > generate separate debian packages out of a manifest yaml file. > > Now the directory structure we are using is: > app/main/[everything for the main front controller] > app/mobile/[everything for the main front controller] > app/admin/[everything for the main front controller] > > Now this actually works quite fine. We did however have to make some > adjustments to createKernel() in the WebTestCase class: > https://gist.github.com/733071
speaking of functional tests, maybe we should also add a base call for command tests? inspiration could be drawn from: https://github.com/knplabs/DoctrineUserBundle/tree/symfony2Security/Tests/Command regards, Lukas Kahwe Smith m...@pooteeweet.org -- 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
