TracMultipleProjects/MultipleEnvironmentsSingleDatabase: trac_data.sql

SET client_encoding = 'UTF8';
SET check_function_bodies = false;
SET client_min_messages = warning;


INSERT INTO component (name, "owner", description) VALUES ('component1', 'somebody', NULL);
INSERT INTO component (name, "owner", description) VALUES ('component2', 'somebody', NULL);


INSERT INTO enum ("type", name, value) VALUES ('status', 'new', '1');
INSERT INTO enum ("type", name, value) VALUES ('status', 'assigned', '2');
INSERT INTO enum ("type", name, value) VALUES ('status', 'reopened', '3');
INSERT INTO enum ("type", name, value) VALUES ('status', 'closed', '4');
INSERT INTO enum ("type", name, value) VALUES ('resolution', 'fixed', '1');
INSERT INTO enum ("type", name, value) VALUES ('resolution', 'invalid', '2');
INSERT INTO enum ("type", name, value) VALUES ('resolution', 'wontfix', '3');
INSERT INTO enum ("type", name, value) VALUES ('resolution', 'duplicate', '4');
INSERT INTO enum ("type", name, value) VALUES ('resolution', 'worksforme', '5');
INSERT INTO enum ("type", name, value) VALUES ('priority', 'blocker', '1');
INSERT INTO enum ("type", name, value) VALUES ('priority', 'critical', '2');
INSERT INTO enum ("type", name, value) VALUES ('priority', 'major', '3');
INSERT INTO enum ("type", name, value) VALUES ('priority', 'minor', '4');
INSERT INTO enum ("type", name, value) VALUES ('priority', 'trivial', '5');
INSERT INTO enum ("type", name, value) VALUES ('ticket_type', 'defect', '1');
INSERT INTO enum ("type", name, value) VALUES ('ticket_type', 'enhancement', '2');
INSERT INTO enum ("type", name, value) VALUES ('ticket_type', 'task', '3');


INSERT INTO milestone (name, due, completed, description) VALUES ('milestone1', 0, 0, NULL);
INSERT INTO milestone (name, due, completed, description) VALUES ('milestone2', 0, 0, NULL);
INSERT INTO milestone (name, due, completed, description) VALUES ('milestone3', 0, 0, NULL);
INSERT INTO milestone (name, due, completed, description) VALUES ('milestone4', 0, 0, NULL);


INSERT INTO permission (username, "action") VALUES ('anonymous', 'LOG_VIEW');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'FILE_VIEW');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'WIKI_VIEW');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'WIKI_CREATE');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'WIKI_MODIFY');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'SEARCH_VIEW');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'REPORT_VIEW');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'REPORT_SQL_VIEW');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'TICKET_VIEW');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'TICKET_CREATE');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'TICKET_MODIFY');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'BROWSER_VIEW');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'TIMELINE_VIEW');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'CHANGESET_VIEW');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'ROADMAP_VIEW');
INSERT INTO permission (username, "action") VALUES ('anonymous', 'MILESTONE_VIEW');


INSERT INTO report (id, author, title, sql, description) VALUES (1, NULL, 'Active Tickets', '
SELECT p.value AS __color__,
   id AS ticket, summary, component, version, milestone, t.type AS type, 
   (CASE status WHEN ''assigned'' THEN owner||'' *'' ELSE owner END) AS owner,
   time AS created,
   changetime AS _changetime, description AS _description,
   reporter AS _reporter
  FROM ticket t, enum p
  WHERE status IN (''new'', ''assigned'', ''reopened'') 
AND p.name = t.priority AND p.type = ''priority''
  ORDER BY p.value, milestone, t.type, time
', '
 * List all active tickets by priority.
 * Color each row based on priority.
 * If a ticket has been accepted, a ''*'' is appended after the owner''s name
');
INSERT INTO report (id, author, title, sql, description) VALUES (2, NULL, 'Active Tickets by Version', '
SELECT p.value AS __color__,
   version AS __group__,
   id AS ticket, summary, component, version, t.type AS type, 
   (CASE status WHEN ''assigned'' THEN owner||'' *'' ELSE owner END) AS owner,
   time AS created,
   changetime AS _changetime, description AS _description,
   reporter AS _reporter
  FROM ticket t, enum p
  WHERE status IN (''new'', ''assigned'', ''reopened'') 
AND p.name = t.priority AND p.type = ''priority''
  ORDER BY (version IS NULL),version, p.value, t.type, time
', '
This report shows how to color results by priority,
while grouping results by version.

Last modification time, description and reporter are included as hidden fields
for useful RSS export.
');
INSERT INTO report (id, author, title, sql, description) VALUES (3, NULL, 'All Tickets by Milestone', '
SELECT p.value AS __color__,
   milestone||'' Release'' AS __group__,
   id AS ticket, summary, component, version, t.type AS type, 
   (CASE status WHEN ''assigned'' THEN owner||'' *'' ELSE owner END) AS owner,
   time AS created,
   changetime AS _changetime, description AS _description,
   reporter AS _reporter
  FROM ticket t, enum p
  WHERE status IN (''new'', ''assigned'', ''reopened'') 
AND p.name = t.priority AND p.type = ''priority''
  ORDER BY (milestone IS NULL),milestone, p.value, t.type, time
', '
This report shows how to color results by priority,
while grouping results by milestone.

Last modification time, description and reporter are included as hidden fields
for useful RSS export.
');
INSERT INTO report (id, author, title, sql, description) VALUES (4, NULL, 'Assigned, Active Tickets by Owner', '

SELECT p.value AS __color__,
   owner AS __group__,
   id AS ticket, summary, component, milestone, t.type AS type, time AS created,
   changetime AS _changetime, description AS _description,
   reporter AS _reporter
  FROM ticket t,enum p
  WHERE status = ''assigned''
AND p.name=t.priority AND p.type=''priority''
  ORDER BY owner, p.value, t.type, time
', '
List assigned tickets, group by ticket owner, sorted by priority.
');
INSERT INTO report (id, author, title, sql, description) VALUES (5, NULL, 'Assigned, Active Tickets by Owner (Full Description)', '
SELECT p.value AS __color__,
   owner AS __group__,
   id AS ticket, summary, component, milestone, t.type AS type, time AS created,
   description AS _description_,
   changetime AS _changetime, reporter AS _reporter
  FROM ticket t, enum p
  WHERE status = ''assigned''
AND p.name = t.priority AND p.type = ''priority''
  ORDER BY owner, p.value, t.type, time
', '
List tickets assigned, group by ticket owner.
This report demonstrates the use of full-row display.
');
INSERT INTO report (id, author, title, sql, description) VALUES (6, NULL, 'All Tickets By Milestone  (Including closed)', '
SELECT p.value AS __color__,
   t.milestone AS __group__,
   (CASE status 
      WHEN ''closed'' THEN ''color: #777; background: #ddd; border-color: #ccc;''
      ELSE 
        (CASE owner WHEN ''$USER'' THEN ''font-weight: bold'' END)
    END) AS __style__,
   id AS ticket, summary, component, status, 
   resolution,version, t.type AS type, priority, owner,
   changetime AS modified,
   time AS _time,reporter AS _reporter
  FROM ticket t,enum p
  WHERE p.name=t.priority AND p.type=''priority''
  ORDER BY (milestone IS NULL), milestone DESC, (status = ''closed''), 
        (CASE status WHEN ''closed'' THEN modified ELSE (-1)*p.value END) DESC
', '
A more complex example to show how to make advanced reports.
');
INSERT INTO report (id, author, title, sql, description) VALUES (7, NULL, 'My Tickets', '
SELECT p.value AS __color__,
   (CASE status WHEN ''assigned'' THEN ''Assigned'' ELSE ''Owned'' END) AS __group__,
   id AS ticket, summary, component, version, milestone,
   t.type AS type, priority, time AS created,
   changetime AS _changetime, description AS _description,
   reporter AS _reporter
  FROM ticket t, enum p
  WHERE t.status IN (''new'', ''assigned'', ''reopened'') 
AND p.name = t.priority AND p.type = ''priority'' AND owner = ''$USER''
  ORDER BY (status = ''assigned'') DESC, p.value, milestone, t.type, time
', '
This report demonstrates the use of the automatically set 
$USER dynamic variable, replaced with the username of the
logged in user when executed.
');
INSERT INTO report (id, author, title, sql, description) VALUES (8, NULL, 'Active Tickets, Mine first', '
SELECT p.value AS __color__,
   (CASE owner 
     WHEN ''$USER'' THEN ''My Tickets'' 
     ELSE ''Active Tickets'' 
    END) AS __group__,
   id AS ticket, summary, component, version, milestone, t.type AS type, 
   (CASE status WHEN ''assigned'' THEN owner||'' *'' ELSE owner END) AS owner,
   time AS created,
   changetime AS _changetime, description AS _description,
   reporter AS _reporter
  FROM ticket t, enum p
  WHERE status IN (''new'', ''assigned'', ''reopened'') 
AND p.name = t.priority AND p.type = ''priority''
  ORDER BY (owner = ''$USER'') DESC, p.value, milestone, t.type, time
', '
 * List all active tickets by priority.
 * Show all tickets owned by the logged in user in a group first.
');


INSERT INTO "system" (name, value) VALUES ('database_version', '16');


INSERT INTO version (name, "time", description) VALUES ('1.0', 0, NULL);
INSERT INTO version (name, "time", description) VALUES ('2.0', 0, NULL);


INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('CamelCase', 1, 1132114161, 'trac', '127.0.0.1', '= !CamelCase =
New words created by smashing together capitalized words.

CamelCase is the original wiki convention for creating hyperlinks, with the additional requirement that the capitals are followed by a lower-case letter; hence “AlabamA” and “ABc” will not be links.

== More information on !CamelCase ==

 * http://c2.com/cgi/wiki?WikiCase
 * http://en.wikipedia.org/wiki/CamelCase

----
See also: WikiPageNames, WikiNewPage, WikiFormatting, TracWiki', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('RecentChanges', 1, 1132114161, 'trac', '127.0.0.1', '= Recent Changes =

[[RecentChanges]]
', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('SandBox', 1, 1132114161, 'trac', '127.0.0.1', '= The Sandbox =

This is just a page to practice and learn WikiFormatting. 

Go ahead, edit it freely.', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('TitleIndex', 1, 1132114161, 'trac', '127.0.0.1', '= Title Index =

[[TitleIndex]]
', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('TracAccessibility', 1, 1132114161, 'trac', '127.0.0.1', '= Accessibility Support in Trac =

Not every user has a graphic environment with a mouse or other pointing device. Some users rely on keyboard, alternative keyboard or voice input to navigate links, activate form controls, etc. In Trac, we work to assure users may interact with devices other than a pointing device.

Trac supports accessibility keys for the most common operations. On Windows and Linux platforms, press any of the keys listed below in combination with the `<Alt>` key; on a Mac, use the `<ctrl>` key instead.

''''Note that when using Internet Explorer on Windows, you need to hit enter after having used the access key.''''

== Global Access Keys ==

 * `1` - WikiStart
 * `2` - [wiki:TracTimeline Timeline]
 * `3` - [wiki:TracRoadmap Roadmap]
 * `4` - [wiki:TracSearch Search]
 * `6` - [wiki:TracGuide Trac Guide / Documentation]
 * `7` - [wiki:TracTickets New Ticket]
 * `9` - [../about About Trac]
 * `0` - This page

----
See also: TracGuide', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('TracAdmin', 1, 1132114161, 'trac', '127.0.0.1', '= TracAdmin =
[[TracGuideToc]]

Trac is distributed with a powerful command-line configuration tool. This tool can be used  to configure and customize your Trac-installation to better fit your needs.

== Usage ==

You can get a comprehensive list of the available options, commands and sub-commands by invoking `trac-admin` with the `help` command:
{{{
trac-admin help
}}}

Unless you''re executing the `help`, `about` or `version` sub-commands, you''ll need to specify the path to the TracEnvironment that you want to administer as the first argument, for example:
{{{
trac-admin /path/to/projenv wiki list
}}}

== Interactive Mode ==

When passing the environment path as the only argument, `trac-admin` starts in interactive mode.
Commands can then be executed on the selected environment using the prompt, which offers tab-completion
(on non-Windows environments, and when the Python `readline` module is available) and automatic repetition of the last command issued.

Once you''re in interactive mode, you can also get help on specific commands or subsets of commands:

For example, to get an explanation of the `resync` command, run:
{{{
> help resync
}}}

To get help on a all the Wiki-related commands, run:
{{{
> help wiki
}}}

----
See also: TracGuide, TracBackup, TracPermissions, TracEnvironment, TracIni
', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('TracBackup', 1, 1132114161, 'trac', '127.0.0.1', '= Trac Backup =
[[TracGuideToc]]

Since Trac uses a database backend, some extra care is required to safely create a backup of a [wiki:TracEnvironment project environment]. Luckily, [wiki:TracAdmin trac-admin] has a command to make backups easier: `hotcopy`.

  ''''Note: Trac uses the `hotcopy` nomenclature to match that of [http://subversion.tigris.org/ Subversion], to make it easier to remember when managing both Trac and Subversion servers.''''

== Creating a Backup ==

To create a backup of a live TracEnvironment, simply run:
{{{
  $ trac-admin /path/to/projenv hotcopy /path/to/backupdir
}}}

[wiki:TracAdmin trac-admin] will lock the database while copying.''''

The resulting backup directory is safe to handle using standard file-based backup tools like `tar` or `dump`/`restore`.

=== Restoring a Backup ===

Backups are simply a copied snapshot of the entire [wiki:TracEnvironment project environment] directory, including the SQLite database. 

To restore an environment from a backup, simply stop the process running Trac (i.e. the Web server or [wiki:TracStandalone tracd]), restore the directory structure from the backup and restart the service.

  ''''Note: Automatic backup of environments that don''t use SQLite as database backend is not supported at this time. As a workaround, we recommend that you stop the server, copy the environment directory, and make a backup of the database using whatever mechanism is provided by the database system.''''

----
See also: TracAdmin, TracEnvironment, TracGuide
', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('TracBrowser', 1, 1132114161, 'trac', '127.0.0.1', '= The Trac Browser =
[[TracGuideToc]]

The Trac browser can be used to browse directories, change logs 
and specific revisions of files stored in a subversion repository.

Directory entries are displayed in a list with sortable columns. The list 
entries can be sorted by ''''name'''', ''''size'''' or ''''age'''' by clicking on the column
headers. The sort order can be reversed by clicking on a given column
header again.

The browser can be used to navigate through the directory structure 
by clicking on the directory names. Clicking on a file name will show
the contents of the file. Clicking on the revision number of a file or
directory will take you to the revision history for that file.

It''s also possible to browse directories or files as they were in history,
at any given repository revision. The default behavior is to display the
latest revision but another revision number can easily be selected using
the ''''View revision'''' input field at the top of the page.

== RSS Support ==

The browser module provided RSS feeds to monitor changes to a file or
directory. To subscribe to an RSS feed for a file or directory, open its
revision log in the browser and click the orange ''XML'' icon at the bottom
of the page. For more information on RSS support in Trac, see TracRss.

----
See also: TracGuide, TracChangeset, FineGrainedPermissions
', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('TracCgi', 1, 1132114161, 'trac', '127.0.0.1', '= Installing Trac as CGI =

To install Trac as a CGI script, you need to make the `trac.cgi` executable as a CGI by your web server. If you''re using [http://httpd.apache.org/ Apache HTTPD], there are a couple ways to do that:

 1. Use a `ScriptAlias` to map a URL to the `trac.cgi` script
 2. Copy the `trac.cgi` file into the directory for CGI executables used by your web server (commonly named `cgi-bin`). You can also create a symbolic link, but in that case make sure that the `FollowSymLinks` option is enabled for the `cgi-bin` directory.

The first option is recommended as it also allows you to map the CGI to a friendly URL.

Now, edit the Apache configuration file and add this snippet, file names and locations changed to match your installation:
{{{
ScriptAlias /trac /usr/share/trac/cgi-bin/trac.cgi

# Trac needs to know where the database is located
<Location "/trac">
  SetEnv TRAC_ENV "/path/to/projectenv"
</Location>
}}}

This will make Trac available at `http://yourhost.example.org/trac`.

 ''''Note: Make sure that the modules mod_alias and mod_env modules are available and enabled in your Apache configuration, otherwise Apache will complain about the above snippet.''''

 ''''Note: If you are using the [http://httpd.apache.org/docs/suexec.html Apache suEXEC] feature see [http://projects.edgewall.com/trac/wiki/ApacheSuexec ApacheSuexec] (on the main Trac site).''''

== Mapping Static Resources ==

Out of the box, Trac will serve static resources such as style sheets or images itself. For a CGI setup, though, this is highly undesirable, because it results in the CGI script being invoked for documents that could be more efficiently served by the web server.

Web servers such as [http://httpd.apache.org/ Apache HTTPD] allow you to create “Aliases” to resources, thereby giving them a virtual URL that doesn''t necessarily bear any resemblance to the layout of the servers file system. We already used this capability above when defining a `ScriptAlias` for the CGI script, and we''ll use it now to map requests to the static resources to the directory on the file system that contains them, thereby bypassing the processing of such requests by the CGI script.

Edit the Apache configuration file again and add the following snippet ''''''before'''''' the `ScriptAlias` for the CGI script , file names and locations changed to match your installation:
{{{
Alias /trac/chrome/common /usr/share/trac/htdocs
<Directory "/usr/share/trac/htdocs">
  Order allow,deny
  Allow from all
</Directory>
}}}

Note that whatever URL path you mapped the `trac.cgi` script to, the path `/chrome/common` is the path you have to append to that location to intercept requests to the static resources. 

For example, if Trac is mapped to `/cgi-bin/trac.cgi` on your server, the URL of the Alias should be `/cgi-bin/trac.cgi/chrome/common`.

Alternatively, you can set the `htdocs_location` configuration option in [wiki:TracIni trac.ini]:
{{{
[trac]
htdocs_location = /trac-htdocs
}}}

Trac will then use this URL when embedding static resources into HTML pages. Of course, you still need to make the Trac `htdocs` directory available through the web server at the specified URL, for example by copying (or linking) the directory into the document root of the web server.

== Adding Authentication ==

The simplest way to enable authentication with Apache is to create a password file. Use the `htpasswd` program to create the password file:
{{{
$ htpasswd -c /somewhere/trac.htpasswd admin
New password: <type password>
Re-type new password: <type password again>
Adding password for user admin
}}}

After the first user, you dont need the "-c" option anymore:
{{{
$ htpasswd /somewhere/trac.htpasswd john
New password: <type password>
Re-type new password: <type password again>
Adding password for user john
}}}

  ''''See the man page for `htpasswd` for full documentation.''''

After you''ve created the users, you can set their permissions using TracPermissions.

Now, you''ll need to enable authentication against the password file in the Apache configuration:
{{{
<Location "/cgi-bin/trac.cgi/login">
  AuthType Basic
  AuthName "Trac"
  AuthUserFile /somewhere/trac.htpasswd
  Require valid-user
</Location>
}}}

For better security, it is recommended that you either enable SSL or at least use the “Digest” authentication scheme instead of “Basic”. Please read the [http://httpd.apache.org/docs/2.0/ Apache HTTPD documentation] to find out more.

----
See also:  TracGuide, TracInstall, TracFastCgi, TracModPython', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('TracChangeset', 1, 1132114161, 'trac', '127.0.0.1', '= Trac Changeset Module =
[[TracGuideToc]]

Trac has a built-in functionality for visualizing “diffs” - changes to files.

When viewing a repository check-in, such as when following a
changeset [wiki:TracLinks link] or a changeset event in the 
[wiki:TracTimeline timeline], Trac will display the exact changes
made by the check-in.

The changeset view consists of two parts, the ''''header'''' and the ''''diff views''''.

== Changeset Header ==

The header shows an overview of the whole changeset.
Here you will find information such as:

 * Timestamp -- When the changeset was commited
 * Author -- Who commited the changeset
 * Message -- A brief description from the author (the commit log message)
 * Files -- A list of files affected by this changeset

In front of each listed file, you''ll find  a colored rectangle. The color
indicates how the file is affected by the changeset.
 
 * Green: Added
 * Red: Removed
 * Yellow: Modified
 * Blue: Copied
 * Gray: Moved

The color legend is located below the header as a reminder.

== Diff Views ==

Below the header is the main part of the changeset, the diff view. Each file is shown in a separate section, each of which will contain only the regions of the file that are affected by the changeset. There are two different styles of displaying the diffs: ''''inline'''' or ''''side-by-side'''' (you can switch between those styles using the preferences form):

 * The ''''inline'''' style shows the changed regions of a file underneath each other. A region removed from the file will be colored red, an added region will be colored green. If a region was modified, the old version is displayed above the new version. Line numbers on the left side indicate the exact position of the change in both the old and the new version of the file.
 * The ''''side-by-side'''' style shows the old version on the left and the new version on the right (this will typically require more screen width than the inline style.) Added and removed regions will be colored in the same way as with the inline style (green and red, respectively), but modified regions will have a yellow background.

In addition, various advanced options are available in the preferences form for adjusting the display of the diffs:
 * You can set how many lines are displayed before and after every change
 * You can toggle whether blank lines, case changes and white space changes are ignored, thereby letting you find the functional changes more quickly

----
See also: TracGuide, TracBrowser
', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('TracEnvironment', 1, 1132114161, 'trac', '127.0.0.1', '= Trac Storage - The Environment =

Trac uses a directory structure and a database for storing project data.

== Creating an Environment ==

A new Trac environment is created using [wiki:TracAdmin trac-admin]:
{{{
$ trac-admin /path/to/projectenv initenv
}}}

[wiki:TracAdmin trac-admin] will ask you for the name of the project, the
database connection string (explained below), and where your subversion
repository is located.

  ''''Note: The web server user will require file system write permission to
the environment directory and all the files inside. Please remember to set
the appropriate permissions. The same applies to the Subversion
repository, although Trac will only require read access as long as you''re
not using the BDB file system.''''

== Database Connection Strings ==

Since version 0.9, Trac supports both [http://sqlite.org/ SQLite] and
[http://www.postgresql.org/ PostgreSQL] as database backends.  The default
is to use SQLite, which is probably sufficient for most projects. The database file
is then stored in the environment directory, and can easily be
[wiki:TracBackup backed up] together with the rest of the environment.

The connection string for an embedded SQLite database is:
{{{
sqlite:db/trac.db
}}}

If you want to use PostgreSQL instead, you''ll have to use a different
connection string. For example, to connect to a database on the same
machine called `trac`, that allows access to the user `johndoe` with
the password `letmein`, use:
{{{
postgres://johndoe:letmein@localhost/trac
}}}

If PostgreSQL is running on a non-standard port (for example 9342), use:
{{{
postgres://johndoe:letmein@localhost:9342/trac
}}}

Note that with PostgreSQL you will have to create the database before running
`trac-admin initenv`.

== Directory Structure ==

An environment directory will usually consist of the following files and directories:

 * `README` - Brief description of the environment.
 * `VERSION` - Contains the environment version identifier.
 * `attachments` - Attachments to wiki pages and tickets are stored here.
 * `conf`
   * `trac.ini` - Main configuration file. See TracIni.
 * `db`
   * `trac.db` - The SQLite database (if you''re using SQLite).
 * `plugins` - Environment-specific [wiki:TracPlugins plugins] (Python eggs)
 * `templates` - Custom environment-specific templates.
   * `site_css.cs` - Custom CSS rules.
   * `site_footer.cs` - Custom page footer.
   * `site_header.cs` - Custom page header.
 * `wiki-macros` - Environment-specific [wiki:WikiMacros Wiki macros].

----
See also: TracAdmin, TracBackup, TracIni, TracGuide
', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('TracFastCgi', 1, 1132114161, 'trac', '127.0.0.1', '= Trac with FastCGI =

Since version 0.9, Trac supports being run through the [http://www.fastcgi.com/ FastCGI] interface. Like [wiki:TracModPython mod_python], this allows Trac to remain resident, and is faster than external CGI interfaces which must start a new process for each request. However, unlike mod_python, it is able to support [http://httpd.apache.org/docs/suexec.html SuEXEC]. Additionally, it is supported by much wider variety of web servers.

== Simple Apache configuration ==
{{{
# Enable fastcgi for .fcgi files
# (If you''re using a distro package for mod_fcgi, something like
# this is probably already present)
<IfModule mod_fastcgi.c>
   AddHandler fastcgi-script .fcgi
   FastCgiIpcDir /var/lib/apache2/fastcgi 
</IfModule>
LoadModule fastcgi_module /usr/lib/apache2/modules/mod_fastcgi.so
}}}

You can either setup the `TRAC_ENV` as an overall default:
{{{
FastCgiConfig -initial-env TRAC_ENV=/path/to/env/trac
}}}

Or you can serve multiple Trac projects in a directory like:
{{{
FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects
}}}

Configure `ScriptAlias` or similar options as described in TracCgi, but calling `trac.fcgi` instead of `trac.cgi`.

== Simple Lighttpd Configuration ==

The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://www.lighttpd.net/ lighttpd].

lighttpd is a secure, fast, compliant and very flexible web-server that has been optimized for high-performance
environments.  It has a very low memory footprint compared to other web servers and takes care of CPU load.

For using `trac.fcgi` with lighttpd add the following to your lighttpd.conf:
{{{
fastcgi.server = ("/trac" =>
                   ("trac" =>
                     ("socket" => "/tmp/trac-fastcgi.sock",
                      "bin-path" => "/path/to/cgi-bin/trac.fcgi",
                      "check-local" => "disable",
                      "bin-environment" =>
                        ("TRAC_ENV" => "/path/to/projenv")
                     )
                   )
                 )
}}}

Note that you will need to add a new entry to `fastcgi.server` for each separate Trac instance that you wish to run. Alternatively, you may use the `TRAC_ENV_PARENT_DIR` variable instead of `TRAC_ENV` as described  above.

Other important information like [http://trac.lighttpd.net/trac/wiki/TracInstall this updated TracInstall page], [wiki:TracCgi#MappingStaticResources and this] are useful for non-fastcgi specific installation aspects.

Relaunch lighttpd, and browse to `http://yourhost.example.org/trac` to access Trac.

----
See also TracCgi, TracModPython, TracInstall, TracGuide', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('TracGuide', 1, 1132114161, 'trac', '127.0.0.1', '= The Trac User and Administration Guide =
[[TracGuideToc]]

The TracGuide is meant to serve as a starting point for all documentation regarding Trac usage and development. The guide is a free document, a collaborative effort, and a part of the [http://projects.edgewall.com/trac/ Trac Project] itself.

== Table of Contents ==
Currently available documentation:
 * TracGuide (This page)  -- Documentation starting point.
   * TracInstall -- How to install and run Trac.
   * TracUpgrade -- How to upgrade existing installations.
   * TracAdmin -- Administrating a Trac project.
   * TracImport -- Importing tickets from other bug databases.
   * TracIni -- Trac configuration file reference. 
   * TracPermissions -- Access control and permissions.
   * TracInterfaceCustomization -- Customizing the Trac interface.
   * TracPlugins -- Installing and managing Trac extensions.
   * TracWiki -- How to use the built-in Wiki.
   * TracBrowser -- Browsing source code with Trac.
   * TracChangeset -- Viewing changes to source code.
   * TracTickets -- Using the issue tracker.
   * TracReports -- Writing and using reports.
   * TracQuery -- Executing custom ticket queries.
   * TracRoadmap -- The roadmap helps tracking project progress.
   * TracTimeline -- The timeline provides a historic perspective on a project.
   * TracLogging -- The Trac logging facility.
   * TracRss -- RSS content syndication in Trac.
   * TracNotification -- Email notification.

 * [http://projects.edgewall.com/trac/wiki/TracFaq Trac FAQ] - A collection of Frequently Asked Questions (on the project website)

== Support and Other Sources of Information ==
If you are looking for a good place to ask a question about Trac, look no further than the [http://projects.edgewall.com/trac/wiki/MailingList MailingList]. It provides a friendly environment to discuss openly among Trac users and developers.

See also the TracSupport page for more information resources.', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('TracImport', 1, 1132114161, 'trac', '127.0.0.1', '= Importing ticket data =

== Bugzilla ==

Ticket data can be imported from Bugzilla using the [http://projects.edgewall.com/trac/browser/trunk/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the contrib/ directory of the Trac distribution.

{{{
$ bugzilla2trac.py
bugzilla2trac - Imports a bug database from Bugzilla into Trac.

Usage: bugzilla2trac.py [options]

Available Options:
  --db <MySQL dbname>              - Bugzilla''s database
  --tracenv /path/to/trac/env      - full path to Trac db environment
  -h | --host <MySQL hostname>     - Bugzilla''s DNS host name
  -u | --user <MySQL username>     - effective Bugzilla''s database user
  -p | --passwd <MySQL password>   - Bugzilla''s user password
  -c | --clean                     - remove current Trac tickets before importing
  --help | help                    - this help info

Additional configuration options can be defined directly in the script.
}}}

Currently, the following data is imported from Bugzilla:

  * bugs
  * bug activity (field changes)
  * bug attachments
  * user names and passwords (put into a htpasswd file)

The script provides a number of features to ease the conversion, such as:

  * PRODUCT_KEYWORDS:  Trac doesn''t have the concept of products, so the script provides the ability to attach a ticket keyword instead.

  * IGNORE_COMMENTS:  Don''t import Bugzilla comments that match a certain regexp.

  * STATUS_KEYWORDS:  Attach ticket keywords for the Bugzilla statuses not available in Trac.  By default, the ''VERIFIED'' and ''RELEASED'' Bugzilla statuses are translated into Trac keywords.

For more details on the available options, see the configuration section at the top of the script.

== Sourceforge ==

Ticket data can be imported from Sourceforge using the [http://projects.edgewall.com/trac/browser/trunk/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution.

== Mantis ==

Mantis bugs can be imported using the attached script.

Currently, the following data is imported from Mantis:
  * bugs
  * bug comments
  * bug activity (field changes)

Attachments are NOT imported.  If you use the script, please read the NOTES section (at the top of the file) and make sure you adjust the config parameters for your environment.

mantis2trac.py has the same parameters as the bugzilla2trac.py script:
{{{
mantis2trac - Imports a bug database from Mantis into Trac.

Usage: mantis2trac.py [options] 

Available Options:
  --db <MySQL dbname>              - Mantis database
  --tracenv /path/to/trac/env      - Full path to Trac db environment
  -h | --host <MySQL hostname>     - Mantis DNS host name
  -u | --user <MySQL username>     - Effective Mantis database user
  -p | --passwd <MySQL password>   - Mantis database user password
  -c | --clean                     - Remove current Trac tickets before importing
  --help | help                    - This help info

Additional configuration options can be defined directly in the script.
}}} 

== Other ==

Since trac uses a SQL database to store the data, you can import from other systems by examining the database tables. Just go into [http://www.sqlite.org/sqlite.html sqlite] command line to look at the tables and import into them from your application.
', NULL, NULL);
INSERT INTO wiki (name, version, "time", author, ipnr, text, "comment", readonly) VALUES ('TracIni', 1, 1132114161, 'trac', '127.0.0.1', '= The Trac Configuration File =
[[TracGuideToc]]

Trac configuration is done by editing the ''''''`trac.ini`'''''' config file, located in `<projectenv>/conf/trac.ini`.

== Global Configuration ==

Since version 0.9, Trac can also read the configuration from a global `trac.ini` file. These global options will then be merged with the environment-specific options, where local options override global options.

The global configuration is by default localted in `$prefix/share/trac/conf/trac.ini`. It can be moved to a different location (for example, `/etc/trac.ini`), but that requires changing the file `trac/siteconfig.py` which gets created when Trac is installed. 

== Reference ==

This is a brief reference of available configuration options.

== [trac] ==