Quoting James Westby (jw+debian@jameswestby.net): > > Template: dtc/conf_hostingpath > > Type: string > > Default: /var/www/sites > > _Description: Path for hosted domains: > > Please enter the directory to be used by DTC to store files for > > all hosted domains. > > . > > 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? I think it isn't. Thomas and I reworded that template again. See #415231 > > My proposed rewording of this: > > > > Template: dtc/conf_use_nated_vhosts > > Type: boolean > > Default: false > > _Description: Use "NATed" vhosts? > > DTC can configure Apache to use one of your IP addresses. If the > > server is firewalled with NAT and port redirections of public IP(s) > > address(es), a "NATed" vhost configuration can be generated. > > . > > 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? Yes, you're right. We reworded again in #415231....
Attachment:
signature.asc
Description: Digital signature