I casually create centralized applications. Put in the folder WEB systems available thus gain a high rate of reuse of classes and specific functions. In addition, clear framework to keep my updated. But the architecture of symfony is perfect and allows you to make extensions or even mix the two architectures.
On 22 abr, 16:48, Rafael Vieira <rafael.vie...@malapronta.com.br> wrote: > Nei and all, > > About this kind of architecture, what do you guys think its the best > option: > > a) Create a centralized application, shared by many websites or > b) Create many applications, one for each website (and all the sites > are the same, with some css customization and different content)? > > What you guys think its the best choice? We know that both formats > have its pros and cons but we're in doubt about wich way to take. > > Any ideas? > > Rafael Vieira > > On 15 abr, 19:03, Nei Rauni Santos <nra...@gmail.com> wrote: > > > Hi guys, > > > Anyone here already created a Symfony's project where the frontend > > application is shared by many websites?? > > I would be happy if you could share this experience with me. > > > I need to recreate an application like this and I'm thinking to do > > this in the following way: > > > - I already has a table called cms.sites.. > > > table: cms.sites > > columns: id, name, url, css, js, .... created_at, updated_at > > > my frontend: > > > - an application frontend > > - a module home > > > I have a filter where it gets the url of request and consult the table > > sites to get info about it, like js, css.... > > > my server: > > >www.example1.com.br > > server: host.test.com > > document_root: /home/example1/site > > >www.example2.com.br > > server: host.test.com > > document_root: /home/example2/site > > >www.example3.com.br > > server: host.test.com > > document_root: /home/example3/site > > > some details: > > > - some directories like js, images and css have a symbolic link to the > > same centralized directory. > > - I have an other application called admin installed in another place > > where I use it to manage the database and to configure the frontends. > > > Some doubts are: > > > - How is the better way to structure the project? > > - Is it better to configure each domain with its own document_root or > > to point all domains to the same document_root? some domains has more > > traffic than others. So, I need that to work fine because if one fail > > all them will also fail. > > > Regards, > > > NeiRauniSantoshttp://blog.inuar.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
