After many comments, here is the 2nd version of the rewritten templates. I mostly adopted all suggestions I could catch, if I'm correct. Please feel free to point me to those I forgot.
Template: shared/zope/restart
Type: select
_Choices: configuring, end, manually
Default: end
_Description: Automatic restart of Zope instances:
Zope offers an extensible, modular structure that allows for the easy
addition of extra components (products) or features. These are
provided as packages with names that start with a 'zope-' prefix.
Each Zope instance needs to be restarted to use any new add-on.
.
Please choose the default behaviour of Zope instances when Zope needs
to be restarted:
.
- configuring: restart instances after each product configuration;
- end: restart instances only once at the end of the whole
installation/upgrading process;
- manually: no automated restart.
Template: zope-common/remove-instance-without-data
Type: select
_Choices: abort, remove and continue
Default: abort
_Description: Action on old/incomplete zope instance '${instance}':
An old/incomplete ${instance} instance was found in
/var/lib/zope${zver}/instance/${instance}, with no Data.fs file.
This installation is either incomplete or incompletely removed.
.
Choosing 'abort' will allow you to inspect the state of the
instance.
.
Choosing 'remove and continue' will remove /var/lib/zope${zver}/instance/${instance}
and reinstall ${instance}. Existing logfiles in
/var/log/zope${zver}/${instance} and configuration files in
/etc/zope${zver}/${instance} will be preserved.
Template: zope-common/keep-data-on-purge
Type: boolean
Default: true
_Description: Keep data for ${instance} on package purge?
Purging the data files of a Zope instance on package purge will
result in the loss of all data for that instance. These data files
are stored in /var/lib/zope${zver}/instance/${instance}.
Template: zope-common/admin-user
Type: string
Default: admin
_Description: Administrative user for '${instance}' Zope instance:
Please enter the login name of the administrative user for the
'${instance}' Zope instance. Valid names must start with a letter and
only include letters and digits.
.
This will only be used for instance creation. Please use the
following command to change the administrative user login name and
password at a later time:
.
/var/lib/zope${zver}/instance/${instance}/bin/zopectl adduser <user> <password>
Template: zope-common/admin-password
Type: password
_Description: Password for the administrative user:
Please enter a password for the administrative user. The password
must not be empty. The password is deleted from the configuration
database once the instance is successfully created and cannot be
recovered.
.
This will only be used for instance creation. Please use the
following command to change the administrative user login name and
password at a later time:
.
/var/lib/zope${zver}/instance/${instance}/bin/zopectl adduser <user> <password>
Template: zope-common/admin-password-confirmation
Type: password
_Description: Password confirmation:
Please confirm the administrative user's password.
Template: zope-common/instance-http-port
Type: string
_Description: HTTP port for this instance:
Please enter the HTTP port number for the ${instance} instance.
.
Other services (e.g. FTP, WebDAV, debug) will be disabled by default.
They can be enabled by editing /etc/zope${zver}/${instance}/zope.conf.
Template: zope-common/instance-zeo-port
Type: string
_Description: TCP port for the ZEO instance:
Please enter the TCP port number for the ${instance} ZEO instance.
Template: zope-common/admin-automatic-password
Type: note
_Description: Automatically generated user and password for this instance
No administrative user login name or password were provided for
this instance. They have been automatically generated.
.
For ${instance} Zope${zver} logins, use the following values:
.
- User : ${user}
- Password : ${password}
Attachment:
signature.asc
Description: Digital signature