Template: shared/zope/restart
Type: select
_Choices: configuring, end, manually
Default: end
_Description: Automatic restart of Zope instances:
 Zope has an extensible, modular structure that allows you to easily
 add extra components (products) or features. Each product or feature
 can usually be found in packages whose name starts with a 'zope-'
 prefix. Unfortunately, each Zope instance needs to be restarted to
 use any new add-on. Here you can choose the default behaviour of
 Zope instances in any installed Zope version when Zope needs to be
 restarted. Each instance, however, is allowed to overwrite this
 setting:
 .
  * configuring: restart instances after each product configuration.
  * end:         restart instances only once at the end of the whole
                 installation/upgrading process.
  * manually:    no restart, it is your responsibility to restart
                 Zope instances.

Template: zope-common/remove-instance-without-data
Type: select
_Choices: abort, remove and continue
Default: abort
_Description: Found an old/incomplete zope instance '${instance}':
 Found an old/incomplete ${instance} instance in
 /var/lib/zope${zver}/instance/${instance}. No data file Data.fs was found
 for the instance, meaning that the installation was not completed
 for some reason, or the installation was incompletely removed.
 Aborting the installation will allow you to inspect the state of the
 instance, continuing will remove /var/lib/zope${zver}/instance/${instance}
 and reinstall the ${instance}. Existing logfiles in
 /var/log/zope${zver}/${instance} and configuration files in
 /etc/zope${zver}/${instance} are 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
 results in loss of all data of the zope instance. The data
 files for this instance are stored in
 /var/lib/zope${zver}/instance/${instance}.

Template: zope-common/admin-user
Type: string
Default: admin
_Description: Admin user for zope instance '${instance}':
 Please enter an admin user for the zope instance '${instance}'.
 A valid user name starts with a letter, followed by letters and digits.
 .
 NOTE: Once the instance has been created, the parameter entered
 here isn't relevant anymore.  To change the admin user (and password)
 later on, call:
 .
 /var/lib/zope${zver}/instance/${instance}/bin/zopectl adduser <user> <password>


Template: zope-common/admin-password
Type: password
_Description: Password for the admin user:
 Please enter a password for the admin user. The password must not be empty.
 The password is deleted from the configuration database, once the
 instance is sucessfully created and cannot be recoverd.
 .
 NOTE: Once the instance has been created, the parameter entered
 here isn't relevant anymore.  To change the admin user (and password)
 later on, call:
 .
 /var/lib/zope${zver}/instance/${instance}/bin/zopectl adduser <user> <password>

Template: zope-common/admin-password-confirmation
Type: password
_Description: Same password:
 Please enter again the password for the admin user.
 .
 NOTE: Once the instance has been created, the parameter entered
 here isn't relevant anymore.  To change the admin user (and password)
 later on, call:
 .
 /var/lib/zope${zver}/instance/${instance}/bin/zopectl adduser <user> <password>

Template: zope-common/instance-http-port
Type: string
_Description: HTTP port for this instance:
 Please enter the HTTP port for the instance ${instance}.
 .
 Other services (e.g. FTP, WebDAV, debug) will be disabled by default.
 You can enable them editing /etc/zope${zver}/${instance}/zope.conf.

Template: zope-common/admin-automatic-password
Type: note
_Description: Automatically generated user and password for your instance
 You haven't provided a user and a password for your instance, so these 
 values have been automatically generated.
 .
 Use these values to log into the Zope${zver} instance ${instance}:
 .
  * User     : ${user}
  * Password : ${password}
