Sounds pretty much as I understood it to be. Yes never put it into those words is all. But I would like to add just one thing. The need to use the mappings are mostly for directories outside the Doucments Directory for the vhost. So had you created

F:/domain_a/myfiles/
and
F:/domain_b/myfiles/

it would have done the same thing without haveing to go to the trouble of creating and using different mapping files at all. I think this was the point that Peter was making.

But I do believe you have it correctly stated.

Chris

[EMAIL PROTECTED] wrote:
Hi guys,

To summarize and close this topic I did some tests and this is
how it works (Sambar V6.1, build 18.May):

1. Create your various vhosts in your vhosts.ini as usual
=> vhosts.ini
[domain_a]
Documents Directory = F:/domain_a/
Mappings File = E:/Programme/sambar60-1/config/domain_a.ini
(...other settings)

[domain_b]
Documents Directory = F:/domain_b/
Mappings File = E:/Programme/sambar60-1/config/domain_b.ini
(...other settings)

Comments:
A) If you don't use the directive 'Mappings File' as shown above, then the aliases are
taken from the mappings.ini and are valid for ALL vhosts which
do NOT use the 'Mappings File' directive
B) You can specify the setting for the Mappings File also in the GUI setup tool for your vhosts under the item 'Mapping/Alias File'


2. Create a specific .ini file for each vhost where you set a value for 'Mappings File'
=> create domain_a.ini
=> create domain_b.ini
and save them in the directory you specified above, ie in our case under
E:/Programme/sambar60-1/config/

3. Now, go into each .ini and set your aliases as needed, for example in
=> domain_a.ini:
[aliases]
/myfiles/ = d:/temp/
/images/ = d:/pictures/
(...other settings)

=> domain_b.ini:
[aliases]
/myfiles/ = d:/downloads/
(...other settings)

Now http://domain_a/myfiles/ = d:/temp
http://domain_a/images/ = d:/pictures
http://domain_b/myfiles/ = d:/downloads
http://domain_b/images/ = error 404


Comments:
As soon as you use the 'Mappings File' directive in your vhosts.ini for
you vhost it does NO longer take any settings from the mappings.ini!
This means, even if you have set ISAPI in mappings.ini you have to do
it again in your mappings.ini specific for that vhost. Also if you set an alias
in your mappings.ini it's NO longer seen by those vhosts, where you used the 'Mappings 
File'
directive.

Hth and makes sense!

Thanks again for your inputs and help,
best regards,

Marcus





















-----------------

:-) well now there you go use the GUI and its already working and I'm
using the May 28th build. Just create your mapping file and put it in config/


vhost.ini
[test]
Automatic Log mailto = CGI Directory = /cgi-bin/
CGI Run As = Default Page = index.htm index.html index.stm index.asp
Documents Directory = F:/test/
Log File = access.log
Mappings File = test_mapping.ini
Messages Directory = messages
SQL AUTH Cache = planet
Search Index = Tmp Directory = tmp
Use MD5 crypt = false
Use SHA1 crypt = false
Use Unix crypt = false
WEB-INF Directory = WebBoard DB Cache = WinCGI Directory = /cgi-win/


-------------------------------------------------------
To unsubscribe please go to http://www.sambar.ch/list/









------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/





Reply via email to