|Version 6 (modified by trac, 4 years ago) (diff)|
The Trac Configuration File
[Note To Editors] Please discuss documentation changes in the #Discussion section. Even better, send us [TracDev/SubmittingPatches documentation patches] against the code (i.e. where the configuration entries are documented), either on Trac-dev or on new tickets.
Table of Contents
Trac configuration is done by editing the trac.ini config file, located in <projectenv>/conf/trac.ini. Changes to the configuration are usually reflected immediately, though changes to the [components] or [logging] sections will require restarting the web server. You may also need to restart the web server after creating a global configuration file when none was previously present.
The trac.ini configuration file and its parent directory should be writable by the web server, as Trac currently relies on the possibility to trigger a complete environment reload to flush its caches.
In versions prior to 0.11, the global configuration was by default located in $prefix/share/trac/conf/trac.ini or /etc/trac/trac.ini, depending on the distribution. If you're upgrading, you may want to specify that file to inherit from. Literally, when you're upgrading to 0.11, you have to add an [inherit] section to your project's trac.ini file. Additionally, you have to move your customized templates and common images from $prefix/share/trac/... to the new location.
Global options will be merged with the environment-specific options, where local options override global options. The options file is specified as follows:
[inherit] file = /path/to/global/trac.ini
Multiple files can be specified using a comma-separated list.
Note that you can also specify a global option file when creating a new project, by adding the option --inherit=/path/to/global/trac.ini to trac-admin's initenv command. If you do not do this but nevertheless intend to use a global option file with your new environment, you will have to go through the newly generated conf/trac.ini file and delete the entries that will otherwise override those set in the global file.
There are two more entries in the [inherit] section, templates_dir for sharing global templates and plugins_dir, for sharing plugins. Those entries can themselves be specified in the shared configuration file, and in fact, configuration files can even be chained if you specify another [inherit] file there.
Note that the templates found in the templates/ directory of the TracEnvironment have precedence over those found in [inherit] templates_dir. In turn, the latter have precedence over the installed templates, so be careful about what you put there, notably if you override a default template be sure to refresh your modifications when you upgrade to a new version of Trac (the preferred way to perform TracInterfaceCustomization being still to write a custom plugin doing an appropriate ITemplateStreamFilter transformation).
Reference for settings
This is a brief reference of available configuration options, and their default settings.
List of email addresses that get notified of user changes, ie, new user, password change and delete user.
Maximum allowed file size (in bytes) for attachments.
Maximum allowed total size (in bytes) for an attachment list to be downloadable as a .zip. Set this to -1 to disable download as .zip. (since 1.0)
Whether attachments should be rendered in the browser, or only made downloadable.
Pretty much any file may be interpreted as HTML by the browser, which allows a malicious user to attach a file containing cross-site scripting attacks.
For public sites where anonymous users can create attachments it is recommended to leave this option disabled (which is the default).
select fields to autocomplement
Resource names that match this pattern will not be added to the breadcrumbs trail.
Text label to show before breadcrumb list. If empty, 'Breadcrumbs:' is used as default.
Indicates maximum number of breadcrumbs to store per user.
List of URL paths to allow breadcrumb tracking. Globs are supported.
Comma-separated list of version control properties to render as oneliner wiki content in the repository browser.
Comma-separated list of version control properties to render as wiki content in the repository browser.
This section is used to enable or disable components provided by plugins, as well as by Trac itself. The component to enable/disable is specified via the name of the option. Whether its enabled is determined by the option value; setting the value to enabled or on will enable the component, any other value (typically disabled or off) will disable the component.
The option name is either the fully qualified name of the components or the module/package prefix of the component. The former enables/disables a specific component, while the latter enables/disables any component in the specified package/module.
Consider the following configuration snippet:
[components] trac.ticket.report.ReportModule = disabled webadmin.* = enabled
The first option tells Trac to disable the report module. The second option instructs Trac to enable all components in the webadmin package. Note that the trailing wildcard is required for module/package matching.
To view the list of active components, go to the Plugins page on About Trac (requires CONFIG_VIEW permissions).
See also: TracPlugins
Default display mode for topic messages list.
Default display mode for forum topics list.
Column by which will be sorted forum lists. Possible values are: id, group, name, subject, time, moderators, description, topics, replies, lasttopic, lastreply.
Direction of forum lists sorting. Possible values are: asc, desc.
Number of messages per page in message list.
Always send discussion notifications to the listed e-mail addresses.
Main navigation bar button title.
Column by which will be sorted topic lists. Possible values are: id, forum, subject, time, author, body, replies, lastreply.
Direction of topic lists sorting. Possible values are: asc, desc.
Number of topics per page in topic list.
This section provides a way to add arbitrary permissions to a Trac environment. This can be useful for adding new permissions to use for workflow actions, for example.
To add new permissions, create a new section [extra-permissions] in your trac.ini. Every entry in that section defines a meta-permission and a comma-separated list of permissions. For example:
[extra-permissions] EXTRA_ADMIN = EXTRA_VIEW, EXTRA_MODIFY, EXTRA_DELETE
This entry will define three new permissions EXTRA_VIEW, EXTRA_MODIFY and EXTRA_DELETE, as well as a meta-permissions EXTRA_ADMIN that grants all three permissions.
The permissions are created in upper-case characters regardless of the casing of the definitions in trac.ini. For example, the definition extra_view would create the permission EXTRA_VIEW.
If you don't want a meta-permission, start the meta-name with an underscore (_):
[extra-permissions] _perms = EXTRA_VIEW, EXTRA_MODIFY
Option for a default naming scheme for new posts. The string can include substitution markers for time (UTC) and user: %Y=year, %m=month, %d=day, %H=hour, %M=minute, %S=second, $USER. Example template string: %Y/%m/%d/my_topic
Ability to specify a list of month names for display in groupings. If empty it will make a list from default locale setting. Enter list of 12 months like: month_names = January, February, ..., December
Option to specify how many recent posts to display on the front page of the Blog (and RSS feeds).
When using the Blog as a personal blog (only one author), setting to 'True' will disable the display of 'Browse by author:' in sidebar, and also removes various author links and references.
Wrap GitRepository in CachedRepository.
Path to the git executable.
Define charset encoding of paths within git repositories.
Enable persistent caching of commit tree.
Path to the base of your git projects
Path to a gitweb-formatted projects.list
Template for project URLs. %s will be replaced with the repo name
The length at which a sha1 should be abbreviated to (must be >= 4 and <= 40).
Enable reverse mapping of git email addresses to trac user ids. Performance will be reduced if there are many users and the cached_repository option is disabled.
A repository resync is required after changing the value of this option.
Use git-committer id instead of git-author id for the changeset Author field.
Use git-committer timestamp instead of git-author timestamp for the changeset Timestamp field.
The minimum length of an hex-string for which auto-detection as sha1 is performed (must be >= 4 and <= 40).
Notify only commits on these branches to Trac
Repository name on GitHub (<user>/<project>)
Change frequency of URLs. Valid values: always, hourly, daily, weekly, monthly, yearly, never. Disabled if empty.
Send sitemap compressed. Useful for larger sitemaps.
Compression level. Value range: 1 (low) to 9 (high). Default: 6
Default entry priority.
Do not list wiki pages from this users (default: "trac")
List of wiki pages to not be included in sitemap
Increased entry priority.
Which realms should be listed. Supported are "wiki", "ticket", "report", "roadmap", "attachment", "browser", "timeline", "homepage", "contactform" and "fullblog".
Notify Google about a new sitemap on the listed actions. Valid values are: TICKET_CREATE, TICKET_DELETE, TICKET_MODIFY, WIKI_CREATE, WIKI_DELETE, WIKI_VERSION_DELETE, WIKI_MODIFY, WIKI_RENAME
Path of sitemap relative to Trac main URL (default: "sitemap.xml"). If this path ends in .gz the sidemap will automatically be compressed.
Should top hierarchical wiki entries have increased priority automatically?
Which top hierarchical wiki entries should be ignored for increased priority.
Wiki pages with increased priority.
The default value to pass along to gravatar to use if the email address does not match.
Alternative text for the header logo.
Height of the header logo image in pixels.
URL to link to, from the header logo.
URL of the image to use as header logo. It can be absolute, server relative or relative.
If relative, it is relative to one of the /chrome locations: site/your-logo.png if your-logo.png is located in the htdocs folder within your TracEnvironment; common/your-logo.png if your-logo.png is located in the folder mapped to the htdocs_location URL. Only specifying your-logo.png is equivalent to the latter.
Width of the header logo image in pixels.
Path to the shared htdocs directory.
Static resources in that directory are mapped to /chrome/shared under the environment URL, in addition to common and site locations.
This can be useful in site.html for common interface customization of multiple Trac environments.
Path to the shared plugins directory.
Plugins in that directory are loaded in addition to those in the directory of the environment plugins, with this one taking precedence.
Path to the shared templates directory.
Templates in that directory are loaded in addition to those in the environments templates directory, but the latter take precedence.
This section configures InterTrac prefixes. Options in this section whose name contain a "." define aspects of the InterTrac prefix corresponding to the option name up to the ".". Options whose name don't contain a "." define an alias.
The .url is mandatory and is used for locating the other Trac. This can be a relative URL in case that Trac environment is located on the same server.
The .title information is used for providing a useful tooltip when moving the cursor over an InterTrac link.
The .compat option can be used to activate or disable a compatibility mode:
- If the targeted Trac is running a version below 0.10 (r3526 to be precise), then it doesn't know how to dispatch an InterTrac link, and it's up to the local Trac to prepare the correct link. Not all links will work that way, but the most common do. This is called the compatibility mode, and is false by default.
- If you know that the remote Trac knows how to dispatch InterTrac links, you can explicitly disable this compatibility mode and then any TracLinks can become InterTrac links.
[intertrac] # -- Example of setting up an alias: t = trac # -- Link to an external Trac: trac.title = Edgewall's Trac for Trac trac.url = http://trac.edgewall.org
Every option in the [interwiki] section defines one InterWiki prefix. The option name defines the prefix. The option value defines the URL, optionally followed by a description separated from the URL by whitespace. Parametric URLs are supported as well.
[interwiki] MeatBall = http://www.usemod.com/cgi-bin/mb.pl? PEP = http://www.python.org/peps/pep-$1.html Python Enhancement Proposal $1 tsvn = tsvn: Interact with TortoiseSvn
If log_type is file, this should be a path to the log-file. Relative paths are resolved relative to the log directory of the environment.
Custom logging format.
If nothing is set, the following will be used:
Trac[$(module)s] $(levelname)s: $(message)s
In addition to regular key names supported by the Python logger library (see http://docs.python.org/library/logging.html), one could use:
Note the usage of $(...)s instead of %(...)s as the latter form would be interpreted by the ConfigParser itself.
Example: ($(thread)d) Trac[$(basename)s:$(module)s] $(levelname)s: $(message)s
Level of verbosity in log.
Should be one of (CRITICAL, ERROR, WARN, INFO, DEBUG).
Logging facility to use.
Should be one of (none, file, stderr, syslog, winlog).
The formats that may be chosen; execute dot -T? for a list of options.
Color of closed tickets
Text for key showing closed tickets
Path to the dot executable.
Show full dep. graph, not just direct blocking links
Direction of the dependency graph (TD = Top Down, DT = Down Top, LR = Left Right, RL = Right Left)
Path to the ghostscript executable.
Highlight target tickets in graph
Color of opened tickets
Text for key showing opened tickets
Show a key for open/closed nodes
If enabled, use ghostscript to produce nicer output.
Maximum file size for HTML preview. (since 0.9)
List of additional MIME types and keyword mappings. Mappings are comma-separated, and for each MIME type, there's a colon (":") separated list of associated keywords or file extensions. (since 0.10)
List of additional MIME types associated to filename patterns. Mappings are comma-separated, and each mapping consists of a MIME type and a Python regexp used for matching filenames, separated by a colon (":"). (since 1.0)
The default style to use for Pygments syntax highlighting.
List of additional MIME types known by Pygments.
For each, a tuple mimetype:mode:quality has to be specified, where mimetype is the MIME type, mode is the corresponding Pygments mode to be used for the conversion and quality is the quality ratio associated to this conversion. That can also be used to override the default quality ratio used by the Pygments render.
Displayed tab width in file preview. (since 0.9)
Comma-separated list of MIME types that should be treated as binary data. (since 0.11.5)
Comma-separated list of domains that should be considered as valid for email addresses (such as localdomain).
Name of the component implementing IEmailSender.
This component is used by the notification system to send emails. Trac currently provides SmtpEmailSender for connecting to an SMTP server, and SendmailEmailSender for running a sendmail-compatible executable. (since 0.12)
Comma-separated list of domains that should not be considered part of email addresses (for usernames with Kerberos domains).
Specifies the MIME encoding scheme for emails.
Valid options are 'base64' for Base64 encoding, 'qp' for Quoted-Printable, and 'none' for no encoding, in which case mails will be sent as 7bit if the content is all ASCII, or 8bit otherwise. (since 0.10)
Path to the sendmail executable.
The sendmail program must accept the -i and -f options. (since 0.12)
Email address(es) to always send notifications to, addresses do not appear publicly (Bcc. (since 0.10)
Email address(es) to always send notifications to, addresses can be seen by all recipients (Cc.
Default host/domain to append to address that do not specify one.
Enable email notification.
Sender address to use in notification emails.
Use the action author as the sender of notification emails. (since 1.0)
Sender name to use in notification emails.
Password for SMTP server. (since 0.9)
SMTP server port to use for email notification.
Reply-To address to use in notification emails.
SMTP server hostname to use for email notifications.
Text to prepend to subject line of notification emails.
If the setting is not defined, then the [$project_name] prefix. If no prefix is desired, then specifying an empty option will disable it. (since 0.10.1)
Username for SMTP server. (since 0.9)
Recipients can see email addresses of other CC'ed recipients.
If this option is disabled (the default), recipients are put on BCC. (since 0.10)
Permit email address without a host/domain (i.e. username only).
The SMTP server should accept those addresses, and either append a FQDN or use local delivery. (since 0.10)
Use SSL/TLS to send notifications over SMTP. (since 0.10)
Disabling this option will prevent all logged in admins from showing up on your Google Analytics reports.
Disabling this option will prevent all authenticated users from showing up on your Google Analytics reports.
Enter any extensions of files you would like to be tracked as a download. For example to track all MP3s and PDFs enter:
Piwik's Site ID.
E-Mail address of the project's administrator.
Base URL of a Trac instance where errors in this Trac should be reported.
This can be an absolute or relative URL, or '.' to reference this Trac instance. An empty value will disable the reporting buttons. (since 0.11.3)
Short description of the project.
Page footer text (right-aligned).
URL of the icon of the project.
Name of the project.
URL of the main project web site, usually the website in which the base_url resides. This is used in notification e-mails.
One of the alternatives for registering new repositories is to populate the [repositories] section of the trac.ini.
This is especially suited for setting up convenience aliases, short-lived repositories, or during the initial phases of an installation.
See TracRepositoryAdmin for details about the format adopted for this section and the rest of that page for the other alternatives.
Additional tags that will be created for submitted screenshots. Possible values are: author, components, versions, name, description.
List of components enabled by default.
Template for embended image description.
Logical relation between component and version part of screenshots filter.
Default format for screenshot download links.
Default format of list item description of [[ScreenshotsList()]] macro.
List of ordering directions for fields specified in default_orders configuration option.
List of names of database fields that are used to sort screenshots.
List of versions enabled by default.
List of screenshot file extensions that can be uploaded. Must be supported by PIL.
List of allowed formats for screenshot download.
Main navigation bar button title.
Meta navigation bar link title.
Path where to store uploaded screenshots.
Number of screenshot columns.
Height of screenshot preview.
Number of screenshot preview rows.
Width of screenshot preview.
Specifies which search filters should be disabled by default on the search page. This will also restrict the filters for the quick search function. The filter names defined by default components are: wiki, ticket, milestone and changeset. For plugins, look for their implementation of the ISearchSource interface, in the get_search_filters() method, the first member of returned tuple. Once disabled, search filters can still be manually enabled by the user on the search page. (since 0.12)
Minimum length of query string allowed when performing a search.
Fields to hide for the simple ticket entry form.
If True, show only the specified fields rather than hiding the specified fields
This section is used to handle all configurations used by spam filter plugin.
Wordpress key required to use the Akismet API.
URL of the Akismet service.
By how many points an Akismet reject impacts the overall karma of a submission.
The karma given to attachments.
The maximum number of bytes from an attachment to pass through the spam filters.
The karma given to authenticated users, in case trust_authenticated is false.
Local file to be loaded to get BadContent. Can be used in addition to BadContent wiki page.
By what factor Bayesian spam probability score affects the overall karma of a submission.
The minimum number of submissions in the training database required for the filter to start impacting the karma of submissions.
URL of the BlogSpam service.
By how many points an BlogSpam reject impacts the overall karma of a submission.
Comma separated list of tests to skip.
API key required to use BotScout.
By how many points a BotScout reject impacts the overall karma of a submission.
CAPTCHA method to use for verifying humans.
Host name for AreYouAHuman usage.
Publisher key for AreYouAHuman usage.
Scoring key for AreYouAHuman usage.
Maximum value of individual terms in numeric CAPTCHA expression.
Number of terms in numeric CAPTCHA expression.
By how many points a failed CAPTCHA impacts the overall score.
Alphabet to choose image CAPTCHA challenge from.
Font size to use in image CAPTCHA.
Set of fonts to choose from when generating image CAPTCHA.
Number of letters to use in image CAPTCHA challenge.
By how many points a successful CAPTCHA response increases the overall score.
Time in seconds that a successful CAPTCHA response increases karma.
Private key for KeyCaptcha usage.
User id for KeyCaptcha usage.
Time in seconds before database cleanup is called.
Private key for reCaptcha usage.
Public key for reCaptcha usage.
Defensio key required to use the API.
URL of the Defensio service.
By how many points a Defensio reject impacts the overall karma of a submission.
List of domains that should be allowed in external links
By how many points too many external links in a submission impact the overall score.
API key required to use FSpamList.
By how many points a FSpamList reject impacts the overall karma of a submission.
Http:BL API key required for use.
By how many points listing as "comment spammer" impacts the overall karma of a submission.
By how many points blacklisting by a single server impacts the overall karma of a submission.
Servers used for IP blacklisting.
By how many points exceeding the configured maximum number of posts per hour impacts the overall score.
Local file to be loaded to get BadIP. Can be used in addition to BadIP wiki page.
By how many points a match with a pattern on the BadIP page impacts the overall karma of a submission.
Interpret X-Forwarded-For header for IP checks.
By how many points a LinkSleeve reject impacts the overall karma of a submission.
Whether all content submissions and spam filtering activity should be logged to the database.
The maximum number of external links allowed in a submission until that submission gets negative karma.
The maximum allowed number of submissions per hour from a single IP address. If this limit is exceeded, subsequent submissions get negative karma.
The minimum score required for a submission to be allowed.
The number of days after which log entries should be purged.
By how many points a match with a pattern on the BadContent page impacts the overall karma of a submission.
The handler used to reject content.
List of page types to add spam report link
By how many points an existing and configured session improves the overall karma of the submission. A third of the points is granted for having an existing session at all, the other two thirds are granted when the user has his name and/or email address set in the session, respectively.
Show the matched bad content patterns in rejection message.
Show the matched bad IP patterns in rejection message.
Show the buttons for training without deleting entry.
Skip external calls when this negative karma is already reached by internal tests.
Skip external calls when this positive karma is already reached by internal tests.
How many monitor entries are displayed by default (between 5 and 10000).
How many report entries are displayed by default (between 5 and 10000).
Default mode for spam user admin panel.
How many days no login are considered for dead accounts.
How many wiki edits are still an unused account.
Stop external calls when this negative karma is reached.
Stop external calls when this positive karma is reached.
API key used to report SPAM.
By how many points a StopForumSpam reject impacts the overall karma of a submission.
Allow training of external services.
By how many points a trap reject impacts the overall karma of a submission.
Name of the invisible trap field, should contain some reference to e-mail for better results.
Name of the hidden trap field, should contain some reference to e-mail for better results.
Whether content submissions by authenticated users should be trusted without checking for potential spam or other abuse.
Allow usage of external services.
Paths to sqlite extensions, relative to Trac environment's directory or absolute. (since 0.12)
base URL of svn repository
Whether the tag cloud should be sorted case-sensitive.
Integer threshold to hide tags with smaller count.
Ticket field to which a drop-down tag list should be attached.
Include partial matches in suggestion list. Default is true.
A list of comma separated values available for input.
Set the default format for the handler of the /tags domain.
Select columns and order for table format using a "|"-separated list of column names.
Supported columns: realm, id, description, tags
Comma-separated list of realms to exclude from tags queries by default, unless specifically included using "realm:realm-name" in a query.
Do not collect tags from closed tickets.
Set default format for the handler of the /tags domain.
See ListTagged description (WikiMacros) for supported values.
Select columns and column order for table format.
See ListTagged description (WikiMacros) for supported values.
Comma-separated list of realms to exclude from tags queries by default, unless specifically included using 'realm:<realm>' in a query.
Number of tagged resources displayed per page of tag query results requested by ListTagged macros and from /tags.
Whether tagged wiki page templates should be queried.
Comma-separated list of realms requiring tag change history.
Character(s) to use as separators between tags. Default is a single whitespace.
List of ticket fields to expose as tags.
If specified, 'keywords' label on ticket view will be turned into a link to this URL.
If true and keywords_help specified, wiki page will open in a new window. Default is false.
Link a tag to the wiki page with same name, if it exists.
Prefix for tag wiki page names.
Status to apply when removing 'Pending' status automatically.
The default moderator for ticket modifications that require moderation, used if the ticket owner and default component owner are not Moderators (since 0.2).
If true (default) email sent to the ticket moderator will not be sent to the smtp_always_cc or smtp_always_bcc addresses (since 0.5).
Notice displayed to users who will be subject to moderation when creating or editing tickets (since 0.6.4).
Text displayed as part of the default confirmation indicating the moderators expected response time (since 0.6).
Publish the assigned Moderator's e-mail address as part of the response to the submitter (since 0.2).
A Genshi text template snippet used to get the notification subject (since 0.2).
Allow users requiring moderation to submit ticket attachments without moderation (since 0.3; deprecated in 0.4, use MODERATOR_PASS_ATTACH permission).
Whether wiki-formatted event messages should be truncated or not.
This only affects the default rendering, and can be overriden by specific event providers, see their own documentation. (Since 0.11)
Default number of days displayed in the Timeline, in days. (since 0.9.)
Maximum number of days (-1 for unlimited) displayable in the Timeline. (since 0.11)
The path to the Subversion authorization (authz) file. To enable authz permission checking, the AuthzSourcePolicy permission policy must be added to [trac] permission_policies.
The module prefix used in the authz_file for the default repository. If left empty, the global section is used.
Inactivity timeout in seconds after which the automatic wiki preview triggers an update. This option can contain floating-point values. The lower the setting, the more requests will be made to the server. Set this to 0 to disable automatic preview. The default is 2.0 seconds. (since 0.12)
Automatically reload template files after modification.
Database backup location
Reference URL for the Trac deployment.
This is the base URL that will be used when producing documents that will be used outside of the web browsing context, like for example when inserting URLs pointing to Trac resources in notification e-mails.
Database connection string for this project
Show the SQL queries in the Trac log, at DEBUG level. (Since 0.11.5)
The date format. Valid options are 'iso8601' for selecting ISO 8601 format, or leave it empty which means the default date format will be inferred from the browser's default language. (since 1.0)
The date information format. Valid options are 'relative' for displaying relative format and 'absolute' for displaying absolute format. (since 1.0)
Name of the component that handles requests to the base URL.
Options include TimelineModule, RoadmapModule, BrowserModule, QueryModule, ReportModule, TicketModule and WikiModule. The default is WikiModule. (since 0.9)
The preferred language to use if no user preference has been set. (since 0.12.1)
The default timezone to use
The maximum number of templates that the template loader will cache in memory. The default value is 128. You may want to choose a higher value if your site uses a larger number of templates, and you have enough memory to spare, or you can reduce it if you are short on memory.
Base URL for serving the core static resources below /chrome/common/.
It can be left empty, and Trac will simply serve those resources itself.
Advanced users can use this together with trac-admin ... deploy <deploydir> to allow serving the static resources for Trac directly from the web server. Note however that this only applies to the <deploydir>/htdocs/common directory, the other deployed resources (i.e. those from plugins) will not be made available this way and additional rewrite rules will be needed in the web server.
An empty value loads jQuery from the copy bundled with Trac.
Alternatively, jQuery could be loaded from a CDN, for example: http://code.jquery.com/jquery-1.7.2.min.js, http://ajax.aspnetcdn.com/ajax/jQuery/jquery-1.7.2.min.js or https://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js.
An empty value loads jQuery UI from the copy bundled with Trac.
Alternatively, jQuery UI could be loaded from a CDN, for example: https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.21/jquery-ui.min.js or http://ajax.aspnetcdn.com/ajax/jquery.ui/1.8.21/jquery-ui.min.js.
An empty value loads the custom Trac jQuery UI theme from the copy bundled with Trac.
Alternatively, a jQuery UI theme could be loaded from a CDN, for example: https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.21/themes/start/jquery-ui.css or http://ajax.aspnetcdn.com/ajax/jquery.ui/1.8.21/themes/start/jquery-ui.css.
Order of the items to display in the mainnav navigation bar, listed by IDs. See also TracNavigation.
Order of the items to display in the metanav navigation bar, listed by IDs. See also TracNavigation.
Location of mysqldump for MySQL database backups
Never obfuscate mailto: links explicitly written in the wiki, even if show_email_addresses is false or the user doesn't have EMAIL_VIEW permission (since 0.11.6).
List of components implementing IPermissionPolicy, in the order in which they will be applied. These components manage fine-grained access control to Trac resources. Defaults to the DefaultPermissionPolicy (pre-0.11 behavior) and LegacyAttachmentPolicy (map ATTACHMENT_* permissions to realm specific ones)
Name of the component implementing IPermissionStore, which is used for managing user and group permissions.
Location of pg_dump for Postgres database backups
Path to the default repository. This can also be a relative path (since 0.11).
This option is deprecated, and repositories should be defined in the repositories section, or using the "Repositories" admin panel. (since 0.12)
List of repositories that should be synchronized on every page request.
Leave this option empty if you have set up post-commit hooks calling trac-admin $ENV changeset added on all your repositories (recommended). Otherwise, set it to a comma-separated list of repository names. Note that this will negatively affect performance, and will prevent changeset listeners from receiving events from the repositories specified here. The default is to synchronize the default repository, for backward compatibility. (since 0.12)
Default repository connector type. (since 0.10)
This is also used as the default repository type for repositories defined in TracIni#repositories-section repositories or using the "Repositories" admin panel. (since 0.12)
Ordered list of filters to apply to all requests (since 0.10).
Restrict cookies to HTTPS connections.
When true, set the secure flag on all cookies so that they are only sent to the server on HTTPS connections. Use this if your Trac instance is only accessible through HTTPS. (since 0.11.2)
Show email addresses instead of usernames. If false, email addresses are obfuscated for users that don't have EMAIL_VIEW permission. (since 0.11)
Show IP addresses for resource edits (e.g. wiki). Since 1.0.5 this option is deprecated and will be removed in 1.3.1. (since 0.11.3)
Timeout value for database connection, in seconds. Use '0' to specify no timeout. (Since 0.11)
Optionally use [trac] base_url for redirects.
In some configurations, usually involving running Trac behind a HTTP proxy, Trac can't automatically reconstruct the URL that is used to access it. You may need to use this option to force Trac to use the base_url setting also for redirects. This introduces the obvious limitation that this environment will only be usable when accessible from that URL, as redirects are frequently used. (since 0.10.5)
If enabled, send contents as chunked encoding in HTTP/1.1. Otherwise, send contents with Content-Length header after entire of the contents are rendered. (since 1.0.6)
When true, send a X-Sendfile header and no content when sending files from the filesystem, so that the web server handles the content. This requires a web server that knows how to handle such a header, like Apache with mod_xsendfile or lighttpd. (since 1.0)
Add a simple toolbar on top of Wiki <textarea>s. (since 1.0.2)
The header to use if use_xsendfile is enabled. If Nginx is used, set X-Accel-Redirect. (since 1.0.6)
List of template names that the plugin will show a WYSIWYG editor on each TracWiki textarea. The plugin shows on all pages by default.
Add stylesheets to the WYSIWYG editor
Base language to be used without prefix/suffix
Page name of table containing available languages
Regular expression to match a language code
Page name template of translated pages
Comma-separated list of allowed prefixes for repository directories when adding and editing repositories in the repository admin panel. If the list is empty, all repository directories are allowed. (since 0.12.1)
List of URL paths to allow voting on. Globs are supported.
Enable/disable highlighting CamelCase links to missing pages (since 0.9).
Maximum allowed wiki page size in characters. (since 0.11.2)
Enable/disable the use of unsafe HTML tags such as <script> or <embed> with the HTML WikiProcessor (since 0.10.4).
For public sites where anonymous users can edit the wiki it is recommended to leave this option disabled (which is the default).
List of URI schemes considered "safe", that will be rendered as external links even if [wiki] render_unsafe_content is false. (since 0.11.8)
Enable/disable splitting the WikiPageNames with space characters (since 0.10).