I have a similar structure actually.. about the "Directory Index" I'm using too!
Have you already created this kind of structure with just one document_root? Thanks, Nei On Apr 16, 4:33 am, Alexandru-Emil Lupu <gang.al...@gmail.com> wrote: > instead of using ln -s, you might wanna do something like in your apache > config: > > server 2: > Alias /css /home/example1/site/web/css > Alias /js /home/example1/site/web/js > > server 3: > Alias /css /home/example1/site/web/css > Alias /js /home/example1/site/web/js > > 2) also ... if your websites are just mirrors why don't you make an alias > and have just one big vhost > 3) if your websites uses different applications of the same project, then > you could change the "directory index" directive in the vhost config and set > it to point to a different page. > Ex: > all doc roots are pointing in the same location, but the "Directory Index" > points out one for index.php (the default) , second for app2.php and 3rd for > app3.php.. > > Do not use symlinks in your application. (except maybe for cache & log dir > if you use capistrano or so for deplyement) > If you have the same frontend, then relax.. if one fails, all will do. :) > > alecs > > On Thu, Apr 16, 2009 at 1:13 AM, HAUSa < > > jeroen_heeft_behoefte_aan_r...@hotmail.com> wrote: > > > Create a symbolic link on your server? > > Search Google for the command ln -s! > > > On 16 apr, 00: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, > > > > Nei Rauni Santoshttp://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 -~----------~----~----~----~------~----~------~--~---
