Re: RFC: common database policy/infrastracture
On Sun, 2004-10-17 at 21:41, Oliver Elphick wrote:
> I attach a diff on the templates file, including questions for a
> PostgreSQL installation..
Well, I do now.
--
Oliver Elphick olly@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
GPG: 1024D/A54310EA 92C8 39E7 280E 3631 3F0E 1EC0 5664 7A2F A543 10EA
========================================
"Trust in the LORD, and do good..." Psalms 37:3
--- database-common.templates.orig 2004-10-17 19:52:16.000000000 +0100
+++ database-common.templates 2004-10-17 21:41:40.000000000 +0100
@@ -4,21 +4,28 @@
Default: ${database_type}
_Description: What database type should ${pkg} use?
${pkg} can be configured to use one of many database types.
- Below, you will be presented with the available choices
+ Below, you will be presented with the available choices. These are
+ database servers installed on this machine or discovered on the
+ local network which can be used to store the data for this package.
Template: database-common/mysql/app_user
Type: string
Default: ${pkg}
_Description: What mysql username should ${pkg} use?
- Please provide a username for ${pkg} to register with the
- database server.
+ Please provide a mysql username for ${pkg} to register with the
+ database server. A mysql user is not necessarily the same as a
+ system login, especially if the database is on a remote server.
+
+ This is the user which will own the database, tables and other
+ objects to be created by this installation. This user will have
+ complete freedom to insert, change or delete data in the database.
Template: database-common/mysql/app_password
Type: string
Default: ${random}
_Description: What mysql password should ${pkg} use?
Please provide a password for ${pkg} to register with the
- database server.
+ database server. This may be left blank if no password is required.
Template: database-common/mysql/host
Type: select
@@ -34,20 +41,81 @@
Template: database-common/mysql/purge
Type: boolean
Default: true
-_Description: Do you want to purge your the mysql database for ${pkg}?
- By default, databases are remove when a package is purged. However, if
+_Description: Do you want to purge the mysql database for ${pkg}?
+ By default, databases are removed when a package is purged. However, if
you would like to retain the database for ${pkg}, this is your last
- chance.
+ chance. Purging the database means that all the data will be irrevocably
+ lost!
Template: database-common/mysql/admin_user
Type: string
Default: root
_Description: What is the name of your database's administrative user?
What is the name of the account with which this package should perform
- administrative actions?
+ administrative actions? This user is the one which is able to create
+ new database users. Note that the mysql user 'root' is NOT the same
+ as the UNIX login 'root'.
Template: database-common/mysql/admin_pw
Type: password
-_Description: What is the name of your database's administrative user?
+_Description: What is the password of your database's administrative user?
What is the password for the account with which this package should perform
administrative actions?
+
+Template: database-common/postgresql/app_user
+Type: string
+Default: ${pkg}
+_Description: What PostgreSQL username should ${pkg} use?
+ Please provide a username for ${pkg} to register with the
+ database server. A PostgreSQL user is not necessarily the same as a
+ system login, especially if the database is on a remote server.
+
+ This is the user which will own the database, schemas, tables and other
+ objects to be created by this installation. This user will have
+ complete freedom to insert, change or delete data in the database or
+ to grant or revoke access to it.
+
+Template: database-common/postgresql/app_password
+Type: string
+Default: ${random}
+_Description: What PostgreSQL password should ${pkg} use?
+ Please provide a password for ${pkg} to register with the
+ database server. PostgreSQL access may need to be reconfigured
+ to allow password-authenticated access.
+
+Template: database-common/postgresql/host
+Type: select
+Choices: local socket
+_Description: What PostgreSQL host should ${pkg} use?
+ Please provide the hostname of the database server for ${pkg}.
+
+Template: database-common/postgresql/host_new
+Type: string
+_Description: What PostgreSQL host should ${pkg} use?
+ Please provide the hostname of the database server for ${pkg}.
+
+Template: database-common/postgresql/purge
+Type: boolean
+Default: true
+_Description: Do you want to purge the PostgreSQL database for ${pkg}?
+ By default, databases are removed when a package is purged. However, if
+ you would like to retain the database for ${pkg}, this is your last
+ chance. Purging the database means that all the data will be irrevocably
+ lost!
+
+Template: database-common/postgresql/admin_user
+Type: string
+Default: postgres
+_Description: What is the name of your database's administrative user?
+ What is the name of the account with which this package should perform
+ administrative actions? This user is the one which is able to create
+ new database users.
+
+Template: database-common/postgresql/admin_pw
+Type: password
+_Description: What is the password of your database's administrative user?
+ What is the password for the account with which this package should perform
+ administrative actions? (For a normal Debian PostgreSQL installation,
+ a database password is not required, since authentication is done at the
+ system level.)
+
Reply to: