Hi, I am seeking opinions. We have a group of about 5 developers and we are engaging in a discussion about how to structure a project. In the past, each developer has made a separate configuration system for various websites. One is reporting, one is configurations and settings, etc.
Now, we are adopting symfony as a framework as these systems are refactored. We want a centralized administrative application, and we want to refactor the old systems all together to be accessed by this one administration system. Now, here is where I am seeking opinions, as none of us are authority's on symfony. Do we: - create a 'backend' and put all the functionality under modules and actions? PROs: CONs: - create a separate APP for each within the PROJECT, and manipulate the routing and layout to be shared for a consistent back end, css, etc? PROs: CONs: That is the conversation that is taking place. Pro's and Con's for keeping them separated by Application or by having everyone use the same backend application and put their functionality into modules and actions. Opinions from experienced symfony developers is highly appreciated. We're really just searching for information (IE: Pro's/Con's) so we can make informed decisions in our planning process. Thanks. -- 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 users" 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-users?hl=en
