[med-svn] r5853 - trunk/packages/ensembl/ensembl/57/debian

[Richard Holland]

Author: holland-guest
Date: 2011-02-02 08:57:13 +0000 (Wed, 02 Feb 2011)
New Revision: 5853

Removed:
   trunk/packages/ensembl/ensembl/57/debian/ensembl.config.template
Log:
Removed redundant Ensembl template.


Deleted: trunk/packages/ensembl/ensembl/57/debian/ensembl.config.template
===================================================================
--- trunk/packages/ensembl/ensembl/57/debian/ensembl.config.template	2011-02-02 08:20:04 UTC (rev 5852)
+++ trunk/packages/ensembl/ensembl/57/debian/ensembl.config.template	2011-02-02 08:57:13 UTC (rev 5853)
@@ -1,136 +0,0 @@
-Template: ensembl/port
-Type: string
-Default: 8000
-Description: Port for Ensembl web interface to listen on
- The Ensembl web interface runs apache underneath. If no other service is
- running on the same machine, the port should most likely be 80, just as
- with regular web services. We presume another web server and/or tomcat
- (8080) to be already running and have chosen port 8000 as a default.
-
-Template: ensembl/webuserdbhost
-Type: string
-Default: localhost
-Description: Port of local database storing user info
- The Ensembl web interface has the option to store temporary
- data locally, so it does not need to transfer all information
- all the time from one web page to another but has those readily
- available in a database.
- .
- This entry specifies the hostname or IP number of the
- machine running the database.
-
-Template: ensembl/webuserdbport
-Type: string
-Default: 3306
-Description: Port of local database storing user info
- The Ensembl web interface has the option to store temporary
- data locally, so it does not need to transfer all information
- all the time from one web page to another but has those readily
- available in a database.
- .
- For most installations, this database will be MySQL,
- which by default listens to port 3306. This may be different
- if that machine has another instance of MySQL already.
-
-Template: ensembl/webuserdbname
-Type: string
-Default: ensembl_web_user_db
-Description: Name of local database storing user info
- The Ensembl web interface has the option to store temporary
- data locally, so it does not need to transfer all information
- all the time from one web page to another but has those readily
- available in a database.
- .
- If you change this name to something else than the default,
- then you don't need any description.
-
-Template: ensembl/webuserdbuser
-Type: string
-Default: ensembl
-Description: Username to access local database storing user info
- The Ensembl web interface has the option to store temporary
- data locally, so it does not need to transfer all information
- all the time from one web page to another but has those readily
- available in a database.
- .
- Security sensitive admins may decide to specify a database user for
- the local database that differs from the default. But the Ensembl
- installation is complex, i.e. you may into unexpected issues when
- diverging from the default. Please start with the default as a start.
-
-Template: ensembl/webuserdbpwd
-Type: password
-Default: ensembl
-Description: Password to access local database storing user info
- The Ensembl web interface has the option to store temporary
- data locally, so it does not need to transfer all information
- all the time from one web page to another but has those readily
- available in a database.
- .
- Security sensitive admins may decide to specify a password for
- that database' user that differs from the default. But the Ensembl
- installation is complex, i.e. you may into unexpected issues when
- diverging from the default. Please start with the default as a start.
-
-Template: ensembl/webuserdbexistyn
-Type: boolean
-Default: false
-Description: Is the web user database already existing?
- The Ensembl web interface has the option to store temporary
- data locally, so it does not need to transfer all information
- all the time from one web page to another but has those readily
- available in a database.
- .
- Please specify with 'Y' if the database does already exist. If
- you answer with 'N', it will be created for you. If 'Y', you
- will be asked if the existing data should be overwritten.
-
-Template: ensembl/webuserdbkeepyn
-Type: boolean
-Default: false
-Description: Shall the web user database be kept?
- The Ensembl web interface has the option to store temporary
- data locally, so it does not need to transfer all information
- all the time from one web page to another but has those readily
- available in a database.
- .
- If you declared the database to be already existing, shall it
- be kept?
-
-Template: ensembl/webuserdbkeeptablesyn
-Type: boolean
-Default: false
-Description: Shall the tables in the web user database be kept?
- Keeping the web user database means you don't have to recreate
- it, but you might want to drop and recreate the tables within it.
- .
- If you didn't keep the database, you don't need to answer this.
- If the database didn't already exist, you don't need to answer.
-
-Template: ensembl/mysqladminuser
-Type: string
-Default: root
-Description: Name of user with admin privileges to local db
- The Ensembl web interface has the option to store temporary
- data locally, so it does not need to transfer all information
- all the time from one web page to another but has those readily
- available in a database.
- .
- To create the database you need special permissions that
- this admin user shall have.
- .
- Only required if the user database does not yet exist.
-
-Template: ensembl/mysqladminpwd
-Type: password
-Default:
-Description: Name of user with admin privileges to local db
- The Ensembl web interface has the option to store temporary
- data locally, so it does not need to transfer all information
- all the time from one web page to another but has those readily
- available in a database.
- .
- This specifies the password with which the admin user can
- access the database.
- .
- Only required if the user database does not yet exist.