On 27.06.2011, at 15:51, [email protected] wrote: > I think a many people use a fontend/backend structure. I couldn't find the > best practice for this in Symfony2.. > > Is there a best practice if you want the frontend and backend in the same > applications? Ideally you have one bundle with the business logic, backend > and frontend code.
the best practice was explained in this thread already: simply create as many frontend controller + kernel's as you need however the key question when putting multiple kernels into one repo is how many custom bundles are shared. if the answer is zero or very few, then i would recommend to use separate repo's for your applications and another repo for each shared bundle. we have a project where lots of entities are shared across the admin, frontend and api kernels so they all sit in one repo for convenience. in another project we have a REST api between the backend and frontend so in the end we only had custom bundle that is shared that we simply put in another repo to easily share it between the two applications. 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
