You dont have to create sumbolic links for each file, if you can identify the shared code, then just put all of it in a directory like "/htdocs/common/" , and then create symbolic links in each of the Sites/VH'S that need to access the common directory (since you can create sym links for directories).
 
This approach might give the hint of exposing files that belong to one site to other sites, but since the code is common they would implicitly be exposed anyway, so I guess you can give it a shot.
 
The site structure might look like this
 
<site1>
/htdocs/site1/common1 -> ../../common
 
<site 2>
/htdocs/site2/common2 -> ../../common
 
......
 
So essentially each site has its own Document root /htdocs/site1, /htdocs/site2, etc, which would contain a folders called common1, common2, etc, each of which are just Sym Links to the directory /htdocs/common/ ...
 
Just my $0.02 ...................
 
 
 
Kishore Jalleda
http://kjalleda.googlepages.com/

 
On 4/25/06, Arnau <[EMAIL PROTECTED]> wrote:
Hi all,

  I have 10 different sites written in php running on linux, each of
them is quite big (some of them with more than 1000 scripts). Theses
sites share the most part of the scripts, I'd say that more of the 95%
of the code is shared among all of them. The problem I have is when I
upload a new version of some file, I have to update all the 10 sites.
I'd like to have the files in just one place and then create links, so
it'd be necessary just to update the files in one place. I was thinking
in creating hard links but you can't create them on directories, and
create a symbolic link for each file is a pain. What you'd recommend me?
I think a lot of people already has had this problem.

Cheers!
--
Arnau

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
  "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to