Re: [RFR] templates://request-tracker3.6/templates
On Wed, Mar 26, 2008 at 05:57:55PM +0100, Christian Perrier wrote:
> Quoting Justin B Rye (jbr@edlug.org.uk):
> > Christian Perrier wrote:
> > > General comment: the templates, particularly the last two are quite
> > > verbose.
> >
> > Here are versions that I've squeezed as hard as I can; they might
> > need to be re-expanded if I've obscured important points.
>
> IMHO, not enough. Why not shorten this down a lot....and point users
> who want details to README.Debian?
Does the attached version look tolerable? I squeezed out what I easily
could from the longer ones.
I also dropped the fix-initialdata-... question altogether and decided
to handle it with dbconfig-common upgrade support. People opting out of
that probably want to fix their databases manually anyway.
Thanks again for your input,
--
Niko Tyni ntyni@debian.org
Template: request-tracker3.6/rtname
Type: string
_Description: Name for this RT instance:
Every installation of Request Tracker must have a unique name.
The domain name or an abbreviation of the name of your organization are
usually good candidates.
.
Please note that once you start using a name, you should probably never
change it. Otherwise, mail for existing tickets won't get put in the right
place.
.
This setting corresponds to the $rtname configuration variable.
Template: request-tracker3.6/organization
Type: string
_Description: Identifier for this RT instance:
In addition to its name, every installation of Request Tracker must also have
a unique identifier. It is used when linking between RT installations.
.
Using this machine's fully qualified hostname (including the DNS domain name)
is recommended.
.
This setting corresponds to the $Organization configuration variable.
Template: request-tracker3.6/correspondaddress
Type: string
_Description: Default email address for RT correspondence:
This address will be listed in From: and Reply-To: headers of
emails tracked by RT, unless overridden by a queue-specific
address.
.
This setting corresponds to the $CorrespondAddress configuration variable.
Template: request-tracker3.6/commentaddress
Type: string
_Description: Default email address for RT comments:
This address will be listed in From: and Reply-To: headers of comment
emails, unless overridden by a queue-specific address. (Comments can be
used for adding ticket information that is not visible to the client.)
.
This setting corresponds to the $CommentAddress configuration variable.
Template: request-tracker3.6/webbaseurl
Type: string
_Description: Base URL to the web interface:
Please specify the scheme, server and (optionally) port for constructing
URLs to the RT web interface.
.
The value should not have a trailing slash (/).
.
This setting corresponds to the $WebBaseURL configuration variable.
Template: request-tracker3.6/webpath
Type: string
_Description: Path to the RT web interface:
If the RT web interface is going to be installed somewhere other than at
the root of your server, you should specify the path to it here.
.
The value requires a leading slash (/) but not a trailing one.
.
This setting corresponds to the $WebPath configuration variable.
Template: request-tracker3.6/handle-siteconfig-permissions
Type: boolean
_Description: Handle RT_SiteConfig.pm permissions?
The RT web interface needs access to the database password, stored in the
main RT configuration file. Because of this, the file is made readable by
the www-data group in normal setups. This may have security implications.
.
If you reject this option, the file will be readable only by root, and
you will have to set up appropriate access controls yourself.
.
Note: with the SQLite backend, your answer will also affect the
permissions of automatically generated local database files.
Reply to: