New debconf template for webcalendar
A new debconf question has been introduced in the webcalendar package and
needs review/translation. The text for this question was stolen from the
gallery2 package, but it would be good if the l10n-english team could review
it.
BTW, I am not sure whether the debconf templates have been ever reviewed
(webcalendar maintainership was taken over recently by Lyz Bevilacqua and
me), so feel free to review the whole file, which is attached below.
Thanks,
--
Rafael Laboissiere
Template: webcalendar/conf/db_persistent
Type: boolean
Default: false
_Description: Use persistent connections?
Using persistent connections can improve performance on heavily loaded
websites by using a previously opened sql connection.
Template: webcalendar/conf/use_http_auth
Type: boolean
Default: false
_Description: Use HTTP auth?
Webcalendar by default uses the database's webcal_user table for
authenticating users. You can use HTTP auth logins instead and use Apache
to manage logins but will still have to add users to webcalendar.
Template: webcalendar/conf/single_user_mode
Type: boolean
Default: false
_Description: Should webcalendar be installed in single user mode?
Webcalendar can be installed in single user mode or multiuser mode. If it
is installed in single user mode, you won't need to login. It isn't
recommended that you install in single user mode unless you are running
this on a personal server protected by a firewall.
Template: webcalendar/conf/single_user_login
Type: string
_Description: Name of the webcalendar user:
If you have installed webcalendar in single user mode, you need to specify
the name of the user to connect as.
Template: webcalendar/status/debconf_managed
Type: boolean
Default: true
_Description: Allow debconf to manage settings.conf?
You can allow debconf to manage your settings.conf or you can manage your
settings manually.
Template: webcalendar/note/admin_user
Type: note
_Description: Webcalendar administrative user
After installing the tables for your sql database you will have access to
webcalendar using the standard admin user. It is STRONGLY suggested that
you change the password after logging in. The default login and password
is admin:admin.
Template: webcalendar/conf/httpd_conf
Type: multiselect
_Choices: apache2, apache, apache-ssl, apache-perl, other
Default: apache2
_Description: Web server to configure:
Apache can be automatically configured to use webcalendar by creating links in
/etc/{apache-version}/conf.d/. Select all the versions of Apache you would
like to automatically configure or 'other' if you don't use Apache or plan on
configuring Apache yourself.
Template: webcalendar/conf/restart_webserver
Type: boolean
Default: false
_Description: Should ${webserver} be restarted?
Remember that in order to activate the new configuration, ${webserver} has
to be restarted. You can also restart ${webserver} by manually executing
'invoke-rc.d ${webserver} restart'.
Template: webcalendar/store/webservers_to_be_restarted
Type: string
Description: Webservers to be restarted:
(This is for internal use only)
Reply to: