Anything on host1 should NOT be viewable of host2 in a normal vhost setup with 2 hosts. It is automatically accomplished. Only if the sounds and images are not in the web root will they need to be mapped and you can map them globally or by vhost.
http://www.vhost1.com/images/ != http://www.vhost2.net/images/ http://www.vhost1.com/sounds/ != http://www.vhost2.net/sounds/ Now I give up. -----Original Message----- From: <[EMAIL PROTECTED]> To: "sambar List Member" <[EMAIL PROTECTED]> Date: Fri, 11 Jun 2004 00:31:28 +0200 Subject: [sambar] Different mappings for different virtual hosts > Jeff, > > Thanks for your mail. What you wrote is what I would like to > accomplish. > >http://www.vhost1.com/images/ != http://www.vhost2.net/images/ > >http://www.vhost1.com/sounds/ != http://www.vhost2.net/sounds/ > This is exactly what I would like to avoid, that 'FolderA' can be > accessed > via domainA AND domainB. And now this is possible because the alias > folders you assign in your mappings.ini can NOT necessarily be accessed > via all vhosts you create. This separation makes lot of sense to me. > > Thanks to all for your help and mails. > > Rgds, > Marcus > > > > ----------------- > >An example might be if you had source/working directories that were > outside > >the web server document path. > > > >Say vhost1 (www.vhost1.com) has audio and image files that are not > >necessarily Web-specific (used outside the Web) and are developed with > >respective applications. A developer would either have to make > duplicate > >copies of each file used on the Web (one for the application, one for > the > >web) or make his/her working directory be under the Web documents > >directory. If you add another vhost (www.vhost2.net) that utilizes > images > >and audio files unrelated to the first vhost but still developed and > >separate objects, the same rules would apply (make two copies or make > the > >application working directory a subdirectory of the Web document > directory. > > > >Instead, you can use common development pathing that points to two > >completely different locations but has the same development structure. > > > >Documents Directory = H:/vhost1/ > >[aliases] > >/images/ = D:/Photoshop/images/travel/ > >/sound/ = C:/Multimedia/sounds/Germany/ > > > >Documents Directory = H:/vhost2/ > >[aliases] > >/images/ = D:/Photoshop/images/museums/ > >/sound/ = C:/Multimedia/sounds/France/ > > > >http://www.vhost1.com/images/ != http://www.vhost2.net/images/ > >http://www.vhost1.com/sounds/ != http://www.vhost2.net/sounds/ > > > >-Jeff > > > >At 05:53 PM 06/09/2004, Peter wrote: > > > >>I just re-read your original post and I can't for the life of me see > why > >>you would need separate vhost mapping to achieve this. > >> > >>"However I would like to use different mappings for different virtual > >>hosts. For example use the folder 'images_a' for vhost A and the > folder > >>'images_b' for vhost B. And the 'b' folder must not be accessable > >>(visible) for vhost A and vice versa. Now I read in the readme for > the 6.1 > >>version: Modified server to allow "mappings.ini" file on a > per-virtual > >>host basis. > >> > >>D:/sambar/ > >>/vhost1/ > >>/images/ > >> > >>D:/sambar/ > >>/vhost2/ > >>/images/ > >> > >>Both hosts are different and separte there is no relationship betweem > them > >>unless you are sharing php and perl globally which would be mapped as > such. > >> > >>To answer your question YES the newest version does support separate > vhost > >>mapping but there will not be any docs until the beta comes out. > >> > >>Peter > > > >------------------------------------------------------- > >To unsubscribe please go to http://www.sambar.ch/list/ > > > > > > > > ------------------------------------------------------- > To unsubscribe please go to http://www.sambar.ch/list/ > > ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
