[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: debconf template: checking of my english for the (source) package dtc



Quoting Dominic Hargreaves (dom@earth.li):
> On Fri, Mar 09, 2007 at 04:48:19PM +0800, Thomas Goirand wrote:
> 
> > I would like to know if any of you would be so kind as to check the
> > spelling and wording of my english template attached to this message for
> > my package dtc.
> 
> I'll look at this during the morning.


I personnally already began a bis rewrite of these templates. See
attached file.


Template: dtc/conf_mysqlhost
Type: string
Default: localhost
_Description: MySQL hostname:
 Please mention the hostname or IP address of the MySQL server.

Template: dtc/conf_mysqllogin
Type: string
Default: root
_Description: MySQL administrator:
 Please mention the login name of a MySQL user with administrative
 privileges. DTC will use it to to grant privileges for its users in
 the tables.

Template: dtc/conf_mysqlpass
Type: password
_Description: MySQL administrator assword:
 Please enter the password of the MySQL administrator.

Template: dtc/conf_mysqldb
Type: string
Default: dtc
_Description: DTC database name:
 All DTC hosting informations are stored in a database.

Template: dtc/conf_mysql_change_root
Type: boolean
Default: false
_Description: Change MySQL root password?
 By default, the mysql-server package does not enforce a password for
 the MySQL root user. This can be changed during the configuration of
 the DTC package.

Template: dtc/main_domainname
Type: string
Default: example.com
_Description: Domain name:
 Please mention the first domain which you want DTC to
 administrate. This domain name will be used to install the root
 admin and customer web control panel of DTC (under one of this domain's
 subdomains).

Template: dtc/dtc_adminsubdomain
Type: string
Default: dtc
_Description: DTC root panel subdomain:
 Please mention the subdomain to be used by DTC control panel.

Template: dtc/conf_ipaddr
Type: string
Default: 192.168.0.2
_Description: Primary IP address:
 Please enter this host's primary IP address. This IP will be used for
 the domain name you just provided, and will be used as default for
 most DTC variables.  If you're using NAT, please enter your external
 IP address.

Template: dtc/conf_hostingpath
Type: string
Default: /var/www/sites
_Description: Path for hosted domains:
 Please mention the directory to be used by DTC to store all hosted domains
 files (mail and web files).
 .
 The default Apache installation defines /var/www as document
 root. This should be manually removed in the httpd.conf file when
 another directory is chosen as DTC's hosting area.

Template: dtc/conf_chroot_path
Type: string
Default: /var/lib/dtc/chroot_template
_Description: Path for the chroot environment:
 Please mention the directory to be used by DTC to build the cgi-bin chroot
 environment template.

Template: dtc/conf_admlogin
Type: string
Default: dtc
_Description: Main domain admin name:
 Each DTC domain must have an administrator. Please enter the login
 name of the administator for the domain name holding the control
 panel installation.

Template: dtc/conf_admpass
Type: password
Default: 
_Description: Main domain admin password:
 Please choose the main domain administrator's password. Access
 to the control panel must be managed manually through an .htpasswd
 file in the  root path.

Template: dtc/conf_mta_type
Type: select
Choices: postfix, qmail
_Description: Mail Transfer Agent (MTA) type:
 Please select the type of the MTA that will be used with DTC. It
 should be already installed on the system. If no such MTA is actually
 installer, please complete the DTC setup of DTC, install a MTA
 package, then run "dpkg-reconfigure dtc".

Template: dtc/conf_use_cyrus
Type: boolean
Default: false
_Description: Use Cyrus mail system?
 Please choose this option if you are using the Cyrus for mail
 delivery, imap and MTA. This option is only compatible with Postfix.

Template: dtc/conf_apache_version
Type: select
Choices: 2, 1
_Description: Apache version to configure:
 DTC supports both Apache and Apache2. Please mention which version
 should be used by with DTC.

Template: dtc/conf_use_nated_vhosts
Type: boolean
Default: false
_Description: Use "nated" vhosts?
 DTC can generate configuration files for Apache to have it use an IP
 address of your server. In case the server is firewalled with NAT and
 port redirections of public IP(s) address(es), you can request for
 the generation of "nated" vhosts.
 .
 Do not choose this option if the server is directly connected to the
 Internet, except when using dynamic IP addresses. In such case, NAT
 and port forwarding are mandatory for DTC.

Template: dtc/conf_nated_vhosts_ip
Type: string
Default: 192.168.0.2
_Description: NATed LAN IP address:
 Please mention the IP address of the server for DTC to
 generate all vhosts that will be used by Apache.

Template: dtc/conf_gen_ssl_cert
Type: boolean
Default: false
_Description: Generate an OpenSSL certificate for DTC?
 If you choose this option, DTC will generate an self signed OpenSSL
 certificate and will use SSL to browse the panel. SSL will also be
 activated and the generated Apache configuration will activate HTTPS
 URLs for the control panel.
 .
 This certificate can later be changed for a root CA certificate.
 .
 Previously generated certificates will never be overwritten. To
 regenerate the certificate, you need to remove all the files in
 /usr/share/dtc/etc/ssl.

Template: dtc/conf_cert_passphrase
Type: password
_Description: DTC certificate passphrase:
 To generate a certificate request and a certificate, OpenSSL needs you
 enter a password. Please type it here.

Template: dtc/conf_cert_countrycode
Type: string
Default: FR
_Description: DTC SSL certificate 2 letters country code:
 Please enter the 2 letter country code of your server location. Example:
 AU, UK, US, FR, DE, etc.

Template: dtc/conf_cert_locality
Type: string
Default: Paris
_Description: DTC SSL certificate city name:
 Please enter the city name of your server location.

Template: dtc/conf_cert_organization
Type: string
Default: GPLHost
_Description: DTC SSL certificate organization name:
 Please enter your organization name.

Template: dtc/conf_cert_unit
Type: string
Default: no-unit
_Description: DTC SSL certificate organization unit:
 Please enter your organization unit name.

Template: dtc/conf_cert_email
Type: string
_Description: DTC SSL certificate email address:
 Please enter your certificate email address.

Template: dtc/conf_cert_challenge_pass
Type: password
_Description: DTC SSL certificate challenge pass:
 Please enter your certificate challenge password.

Template: dtc/conf_upgrade_pear
Type: boolean
Default: true
_Description: Update pear installation?
 You can ask DTC to check your pear installation during install. This
 REQUIRES a network connection to the internet. If you can't do so here,
 please check that you have the following PEAR modules up-to-date:
 Crypt_CBC and Auth_SASL. The files should be in /usr/share/php if you
 want to check.

Template: dtc/conf_dnsbl_list
Type: string
Default: sbl-xbl.spamhaus.org,list.dsbl.org,relays.ordb.org
_Description: DNSBL (DNS BlackList) list:
 Please enter the list of preferred DNSBL servers to add to your Postfix
 mail server configuration.

Template: dtc/conf_eth2monitor
Type: string
_Description: Network devices to monitor:
 Please enter here all the network devices you wish to be monitored by the
 RRDTools graphing.

Template: dtc/conf_report_setup_stat
Type: boolean
Default: true
_Description: Allow to report anonymous statistic to GPLHost?
 You can help GPLHost to know how many DTC setup has been done, by
 reporting your installation to it's web site. No data will be collected
 except the operating system (Debian in your case), IP address of the setup
 (the IP is used as an identifier so GPLHost don't account upgrades and/or
 reinstallations, it will never be used for commercial purpose). You have
 to be connected to internet and wget must be installed to do the report.

Template: dtc/conf_omit_dev_mknod
Type: boolean
Default: false
_Description: Skip mknod calls when building chroot template?
 In some environment, like Linux vServer, mknod is not allowed to be
 executed. For that reason, it's possible to skip the creation of the dev
 null, random and urandom devices during the chroot template creation.

Attachment: signature.asc
Description: Digital signature


Reply to: