James Westby wrote:
>> If you choose /var/www, which is Apache's default document root, all
>> files hosted in that directory will become publicly accessible. It is
>> therefore recommended to choose another directory if the local web
>> server is hosting other files in /var/www.
>
> Does the default of /var/www/sites suffer from this issue?
It used to, it doesn't any more since we take over the Listen directive.
But I consider it a good warning to explain what's happening.
>> This option should be chosen only if the server is directly connected
>> to the Internet and uses a dynamic public IP addres. In such cases,
>> NAT and port forwarding are mandatory for DTC.
>>
>>
>
> This still seems to be in conflict with Thomas' meaning of the
> templates. He says
>
> Do not choose this option if the server is directly connected to the
> internet.
>
> whereas your suggestion is
>
> This option should be chosen only if the server is directly connected
> to the Internet.
>
> Is there some misunderstanding here of the use of "directly connected"
> in this context?
>
> Thanks,
>
> James
You are right, it should be:
This option should be chosen only if the server is *NOT* directly
connected to the Internet
If it's more clear with it, that means something like that (the stars
are Ethernet interfaces with IP addresses):
[Internet] --- * router doing NAT * --- [LAN] --- * Server behind NAT
Public-IP LAN-IP-1 LAN-IP-2
If it's like that, then the NAT option should be chosen. If the Public
IP is a dynamic IP that changes often, then this is the only way to have
the DTC system working because Apache vhosts.conf file would have to be
regenerated with the new IP all the time otherwise (with new Listen
IP:port directives and <VirtualHost IP:port> directives), and currently
it simply can't do it (I'm not even sure it will one day).
Is more easy to understand like that???
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
