# wiki

name: TracReports
author: trac
ipnr: 127.0.0.1
text:
  = Trac Reports =
  [[TracGuideToc]]

  The Trac reports module provides a simple, yet powerful reporting facility
  to present information about tickets in the Trac database.

  Rather than have its own report definition format, TracReports relies on standard SQL
  `SELECT` statements for custom report definition. 

    '''Note:''' ''The report module is being phased out in its current form because it seriously limits the ability of the Trac team to make adjustments to the underlying database schema. We believe that the [wiki:TracQuery query module] is a good replacement that provides more flexibility and better usability. While there are certain reports that cannot yet be handled by the query module, we intend to further enhance it so that at some point the reports module can be completely removed. This also means that there will be no major enhancements to the report module anymore.''

    ''You can already completely replace the reports module by the query module simply be disabling the former in [wiki:TracIni trac.ini]:''
    {{{
    [components]
    trac.ticket.report.* = disabled
    }}}
    ''This will make the query module the default handler for the “View Tickets” navigation item. We encourage you to try this configuration and report back what kind of features of reports you are missing, if any.''

  A report consists of these basic parts:
   * '''ID''' -- Unique (sequential) identifier 
   * '''Title'''  -- Descriptive title
   * '''Description'''  -- A brief description of the report, in WikiFormatting text.
   * '''Report Body''' -- List of results from report query, formatted according to the methods described below.
   * '''Footer''' -- Links to alternative download formats for this report.

  == Changing Sort Order ==
  Simple reports - ungrouped reports to be specific - can be changed to be sorted by any column simply by clicking the column header. 

  If a column header is a hyperlink (red), click the column you would like to sort by. Clicking the same header again reverses the order.


  == Alternate Download Formats ==
  Aside from the default HTML view, reports can also be exported in a number of alternate formats.
  At the bottom of the report page, you will find a list of available data formats. Click the desired link to 
  download the alternate report format.

  === Comma-delimited - CSV (Comma Separated Values) ===
  Export the report as plain text, each row on its own line, columns separated by a single comma (',').
  '''Note:''' Carriage returns, line feeds, and commas are stripped from column data to preserve the CSV structure.

  === Tab-delimited ===
  Like above, but uses tabs (\t) instead of comma.

  === RSS - XML Content Syndication ===
  All reports support syndication using XML/RSS 2.0. To subscribe to an RSS feed, click the orange 'XML' icon at the bottom of the page. See TracRss for general information on RSS support in Trac.

  ----

  == Creating Custom Reports ==

  ''Creating a custom report requires a comfortable knowledge of SQL.''

  A report is basically a single named SQL query, executed and presented by
  Trac.  Reports can be viewed and created from a custom SQL expression directly
  in from the web interface.

  Typically, a report consists of a SELECT-expression from the 'ticket' table,
  using the available columns and sorting the way you want it.

  == Ticket columns ==
  The ''ticket'' table has the following columns:
   * id
   * time
   * changetime
   * component
   * severity  
   * priority 
   * owner
   * reporter
   * cc
   * version
   * milestone
   * status
   * resolution
   * summary
   * description

  See TracTickets for a detailed description of the column fields.

  '''all active tickets, sorted by priority and time'''

  '''Example:''' ''All active tickets, sorted by priority and time''
  {{{
  SELECT id AS ticket, status, severity, priority, owner, 
         time as created, summary FROM ticket 
    WHERE status IN ('new', 'assigned', 'reopened')
    ORDER BY priority, time
  }}}


  ----


  == Advanced Reports: Dynamic Variables ==
  For more flexible reports, Trac supports the use of ''dynamic variables'' in report SQL statements. 
  In short, dynamic variables are ''special'' strings that are replaced by custom data before query execution.

  === Using Variables in a Query ===
  The syntax for dynamic variables is simple, any upper case word beginning with '$' is considered a variable.

  Example:
  {{{
  SELECT id AS ticket,summary FROM ticket WHERE priority='$PRIORITY'
  }}}

  To assign a value to $PRIORITY when viewing the report, you must define it as an argument in the report URL, leaving out the the leading '$'.

  Example:
  {{{
   http://projects.edgewall.com/trac/reports/14?PRIORITY=high
  }}}

  To use multiple variables, separate them with an '&'.

  Example:
  {{{
   http://projects.edgewall.com/trac/reports/14?PRIORITY=high&SEVERITY=critical
  }}}


  === Special/Constant Variables ===
  There is one ''magic'' dynamic variable to allow practical reports, its value automatically set without having to change the URL. 

   * $USER -- Username of logged in user.

  Example (''List all tickets assigned to me''):
  {{{
  SELECT id AS ticket,summary FROM ticket WHERE owner='$USER'
  }}}


  ----


  == Advanced Reports: Custom Formatting ==
  Trac is also capable of more advanced reports, including custom layouts,
  result grouping and user-defined CSS styles. To create such reports, we'll use
  specialized SQL statements to control the output of the Trac report engine.

  == Special Columns ==
  To format reports, TracReports looks for 'magic' column names in the query
  result. These 'magic' names are processed and affect the layout and style of the 
  final report.

  === Automatically formatted columns ===
   * '''ticket''' -- Ticket ID number. Becomes a hyperlink to that ticket. 
   * '''created, modified, date, time''' -- Format cell as a date and/or time.

   * '''description''' -- Ticket description field, parsed through the wiki engine.

  '''Example:'''
  {{{
  SELECT id as ticket, created, status, summary FROM ticket 
  }}}

  === Custom formatting columns ===
  Columns whose names begin and end with 2 underscores (Example: '''_''''''_color_''''''_''') are
  assumed to be ''formatting hints'', affecting the appearance of the row.
   
   * '''_''''''_group_''''''_''' -- Group results based on values in this column. Each group will have its own header and table.
   * '''_''''''_color_''''''_''' -- Should be a numeric value ranging from 1 to 5 to select a pre-defined row color. Typically used to color rows by issue priority.
   * '''_''''''_style_''''''_''' -- A custom CSS style expression to use for the current row. 

  '''Example:''' ''List active tickets, grouped by milestone, colored by priority''
  {{{
  SELECT p.value AS __color__,
       t.milestone AS __group__,
       (CASE owner WHEN 'daniel' THEN 'font-weight: bold; background: red;' ELSE '' END) AS __style__,
         t.id AS ticket, summary
    FROM ticket t,enum p
    WHERE t.status IN ('new', 'assigned', 'reopened') 
      AND p.name=t.priority AND p.type='priority'
    ORDER BY t.milestone, p.value, t.severity, t.time
  }}}

  '''Note:''' A table join is used to match ''ticket'' priorities with their
  numeric representation from the ''enum'' table.

  === Changing layout of report rows ===
  By default, all columns on each row are display on a single row in the HTML
  report, possibly formatted according to the descriptions above. However, it's
  also possible to create multi-line report entries.

   * '''column_''' -- ''Break row after this''. By appending an underscore ('_') to the column name, the remaining columns will be be continued on a second line.

   * '''_column_''' -- ''Full row''. By adding an underscore ('_') both at the beginning and the end of a column name, the data will be shown on a separate row.

   * '''_column'''  --  ''Hide data''. Prepending an underscore ('_') to a column name instructs Trac to hide the contents from the HTML output. This is useful for information to be visible only if downloaded in other formats (like CSV or RSS/XML).

  '''Example:''' ''List active tickets, grouped by milestone, colored by priority, with  description and multi-line layout''

  {{{
  SELECT p.value AS __color__,
         t.milestone AS __group__,
         (CASE owner 
            WHEN 'daniel' THEN 'font-weight: bold; background: red;' 
            ELSE '' END) AS __style__,
         t.id AS ticket, summary AS summary_,             -- ## Break line here
         component,version, severity, milestone, status, owner,
         time AS created, changetime AS modified,         -- ## Dates are formatted
         description AS _description_,                    -- ## Uses a full row
         changetime AS _changetime, reporter AS _reporter -- ## Hidden from HTML output
    FROM ticket t,enum p
    WHERE t.status IN ('new', 'assigned', 'reopened') 
      AND p.name=t.priority AND p.type='priority'
    ORDER BY t.milestone, p.value, t.severity, t.time
  }}}

  === Reporting on custom fields ===

  If you have added custom fields to your tickets (experimental feature in v0.8, see TracTicketsCustomFields), you can write a SQL query to cover them. You'll need to make a join on the ticket_custom table, but this isn't especially easy.

  If you have tickets in the database ''before'' you declare the extra fields in trac.ini, there will be no associated data in the ticket_custom table. To get around this, use SQL's "LEFT OUTER JOIN" clauses. See TracIniReportCustomFieldSample for some examples.

  ----
  See also: TracTickets, TracQuery, TracGuide


name: TracModPython
author: trac
ipnr: 127.0.0.1
text:
  = Trac and mod_python =

  Trac supports [http://www.modpython.org/ mod_python], which speeds up Trac's response times considerably and permits use of many Apache features not possible with [wiki:TracStandalone tracd]/mod_proxy.

  == Simple configuration ==

  If you just installed mod_python, you may have to add a line to load the module in the Apache configuration:
  {{{
  LoadModule python_module modules/mod_python.so
  }}}

  A simple setup of Trac on mod_python looks like this:
  {{{
  <Location /projects/myproject>
     SetHandler mod_python
     PythonHandler trac.web.modpython_frontend 
     PythonOption TracEnv /var/trac/myproject
     PythonOption TracUriRoot /projects/myproject
  </Location>
  }}}

  Note that the option `TracUriRoot` may or may not be necessary in your setup. Try without first, and if the URLs produced by Trac look wrong or if Trac does not seem to recognize the URLs correctly, add the `TracUriRoot` option.

  Configuring authentication works the same as for [wiki:TracCgi#AddingAuthentication CGI]:
  {{{
  <Location "/projects/myproject/login">
    AuthType Basic
    AuthName "myproject"
    AuthUserFile /var/trac/myproject/.htaccess
    Require valid-user
  </Location>
  }}}

  If the Trac installation isn't installed in your Python path, you'll have to tell Apache where to find the Trac mod_python handler  using the `PythonPath` directive:
  {{{
  <Location /projects/myproject>
    ...
    PythonPath "sys.path + ['/path/to/trac']"
    ...
  </Location>
  }}}


  == Setting up multiple projects ==

  The Trac mod_python handler handler supports a configuration option similar to Subversion's `SvnParentPath`, called `TracEnvParentDir`:
  {{{
  <Location /projects>
    SetHandler mod_python
    PythonHandler trac.web.modpython_frontend 
    PythonOption TracEnvParentDir /var/trac
    PythonOption TracUriRoot /projects
  </Location>
  }}}

  When you request the `/projects` URL, you will get a listing of all subdirectories of the directory you set as `TracEnvParentDir`. Selecting any project in the list will bring you to the corresponding Trac environment.

  If you don't want to have the subdirectory listing as your projects home page you can use a
  {{{
  <LocationMatch "/.+/">
  }}}

  This will instruct Apache to use mod_python for all locations different from root while having the possibility of placing a custom home page for root in your !DocumentRoot folder.

  You can also use the same authentication realm for all of the projects using a `<LocationMatch>` directive:
  {{{
  <LocationMatch "/[^/]+/login">
    AuthType Basic
    AuthName "Trac"
    AuthUserFile /var/trac/.htaccess
    Require valid-user
  </LocationMatch>
  }}}

  == Virtual Host Configuration ==

  Below is the sample configuration required to set up your trac as a virtual server (i.e. when you access it at the URLs like
  !http://trac.mycompany.com):

  {{{
  <VirtualHost * >
      DocumentRoot /var/trac/myproject
      ServerName trac.mycompany.com
      <Directory />
          SetHandler mod_python
          PythonHandler trac.web.modpython_frontend
          PythonOption TracEnv /var/trac/myproject
          PythonOption TracUriRoot /
      </Directory>
      <Location /login>
          AuthType Basic
          AuthName "MyCompany Trac Server"
          AuthUserFile /var/trac/myproject/.htusers
          Require valid-user
      </Location>
  </VirtualHost>
  }}}

  == Troubleshooting ==

  === Form submission problems ===

  If you're experiencing problems submitting some of the forms in Trac (a common problem is that you get redirected to the start page after submission), check whether your {{{DocumentRoot}}} contains a folder or file with the same path that you mapped the mod_python handler to. For some reason, mod_python gets confused when it is mapped to a location that also matches a static resource.

  === Using .htaccess ===

  Although it may seem trivial to rewrite the above configuration as a directory in your document root with a `.htaccess` file, this does not work. Apache will append a "/" to any Trac URLs, which interferes with its correct operation.

  It may be possible to work around this with mod_rewrite, but I failed to get this working. In all, it is more hassle than it is worth. Stick to the provided instructions. :)

  === Win32 Issues ===

  If you run trac with mod_python (3.1.3 or 3.1.4) on Windows, 
  uploading attachments will '''not''' work.
  This is a known problem which we can't solve cleanly at the Trac level.

  However, there is a workaround for this at the mod_python level, 
  which is to apply the following patch [http://projects.edgewall.com/trac/attachment/ticket/554/util_py.patch attachment:ticket:554:util_py.patch] 
  to the (Lib/site-packages)/modpython/util.py file.

  If you don't have the `patch` command, that file can be replaced with the [http://svn.apache.org/viewcvs.cgi/httpd/mod_python/trunk/lib/python/mod_python/util.py?rev=103562&view=markup  fixed util.py] (fix which, although done prior to the 3.1.4 release, is ''not'' 
  present in 3.1.4).

  === OS X issues ===

  When using mod_python on OS X you will not be able to restart Apache using `apachectl restart`. This is apparently fixed in mod_python 3.2, but there's also a patch available for earlier versions [http://www.dscpl.com.au/projects/vampire/patches.html here].

  ----
  See also TracGuide, TracInstall, TracCgi, TracFastCgi


name: TracNotification
author: trac
ipnr: 127.0.0.1
text:
  = Email Notification of Ticket Changes =
  [[TracGuideToc]]

  Trac supports basic notification for ticket changes using email. 

  Email notification is useful to keep users up-to-date on tickets/issues of interest, and also provides a convenient way to post ticket changes to a dedicated mailing list. '''Note:''' As an example, this is how the [http://lists.edgewall.com/archive/trac-tickets/ Trac-tickets] mailing list works.

  Disabled by default, notification can be activated and configured in [wiki:TracIni trac.ini].

  == Receiving Notification ==
  When reporting a new ticket or adding a comment, enter a valid email address in the ''reporter'', ''editor'' or ''cc'' field. Trac will automatically send you an email when changes are made to the ticket.

  This is useful to keep up-to-date on an issue or enhancement request that interests you.

  == Configuring SMTP Notification ==

  === Configuration Options ===
  These are the available options for the ''[notification]'' section in trac.ini.
   * '''smtp_enabled''': Enable email notification.
   * '''smtp_server''': SMTP server used for notification messages.
   * '''smtp_user''': (''requires [milestone:0.9 0.9]'') user name for authentication SMTP account.
   * '''smtp_password''': (''requires [milestone:0.9 0.9]'') password for authentication SMTP account.
   * '''smtp_from''': Email address to use for ''Sender''-headers in notification emails.
   * '''smtp_replyto''': Email address to use for ''Reply-To''-headers in notification emails.
   * '''smtp_always_cc''': List of email addresses to always send notifications to. ''Typically used to post ticket changes to a dedicated mailing list.''
   * '''always_notify_reporter''':  Always send notifications to any address in the reporter field.
   * '''always_notify_owner''': (''requires [milestone:0.9 0.9]'') Always send notifications to the address in the owner field.

  Either '''smtp_from''' or '''smtp_replyto''' (or both) ''must'' be set, otherwise Trac refuses to send notification mails.

  === Example Configuration ===

  {{{
  [notification]
  smtp_enabled = true
  smtp_server = mail.example.com
  smtp_from = notifier@example.com
  smtp_replyto = myproj@projects.example.com
  smtp_always_cc = ticketmaster@example.com, theboss+myproj@example.com
  }}}

  == Sample Email ==
  {{{
  #42: testing
  ---------------------------+------------------------------------------------
         Id:  42             |      Status:  assigned                
  Component:  report system  |    Modified:  Fri Apr  9 00:04:31 2004
   Severity:  major          |   Milestone:  0.9                     
   Priority:  lowest         |     Version:  0.6                     
      Owner:  anonymous      |    Reporter:  jonas@example.com               
  ---------------------------+------------------------------------------------
  Changes:
    * component:  changset view => search system
    * priority:  low => highest
    * owner:  jonas => anonymous
    * cc:  daniel@example.com =>
           daniel@example.com, jonas@example.com
    * status:  new => assigned

  Comment:
  I'm interested too!

  --
  Ticket URL: <http://example.com/trac/ticket/42>
  My Project <http://myproj.example.com/>
  }}}
  ----
  See also: TracTickets, TracIni, TracGuide


name: TracRoadmap
author: trac
ipnr: 127.0.0.1
text:
  = The Trac Roadmap =
  [[TracGuideToc]]

  The roadmap provides a view on the [wiki:TracTickets ticket system] that helps planning and managing the future development of a project.

  == The Roadmap View ==

  Basically, the roadmap is just a list of future milestones. You can add a description to milestones (using WikiFormatting) describing main objectives, for example. In addition, tickets targeted for a milestone are aggregated, and the ratio between active and resolved tickets is displayed as a milestone progress bar.

  == The Milestone View ==

  It is possible to drill down into this simple statistic by viewing the individual milestone pages. By default, the active/resolved ratio will be grouped and displayed by component. You can also regroup the status by other criteria, such as ticket owner or severity. Ticket numbers are linked to [wiki:TracQuery custom queries] listing corresponding tickets.

  == Roadmap Administration ==

  It is possible to add, modify and remove milestones using either TracAdmin or the web interface. 

  '''Note:''' Milestone descriptions can currently only be edited from the web interface. With appropriate permissions, you'll see buttons for milestone management on the roadmap and milestone pages.

  == iCalendar Support ==

  The Roadmap supports the [http://www.ietf.org/rfc/rfc2445.txt iCalendar] format to keep track of planned milestones and related tickets from your favorite calendar software. Calendar applications supporting the iCalendar specification include [http://www.apple.com/ical/ Apple iCal] for Mac OS X and the cross-platform [http://www.mozilla.org/projects/calendar/ Mozilla Calendar]. [http://kdepim.kde.org/components/korganizer.php Korganiser] (the calendar application of the [http://www.kde.org/ KDE] project) and [http://www.novell.com/de-de/products/desktop/features/evolution.html Evolution] also support iCalendar.

  To subscribe to the roadmap, copy the iCalendar link from the roadmap (found at the bottom of the page) and choose the "Subscribe to remote calendar" action (or similar) of your calendar application, and insert the URL just copied.

  '''Note:''' For tickets to be included in the calendar as tasks, you need to be logged in when copying the link. You will only see tickets assigned to yourself, and associated with a milestone.

  More information about iCalendar can be found at [http://en.wikipedia.org/wiki/ICalendar Wikipedia].
  ----
  See also: TracTickets, TracReports, TracQuery, TracGuide


name: WikiDeletePage
author: trac
ipnr: 127.0.0.1
text:
  = Deleting a Wiki Page =

  Existing wiki pages can be completely deleted using the ''Delete Page'' or the ''Delete this Version'' buttons at the bottom of the wiki page. These buttons are only visible for users with `WIKI_DELETE` permissions.

  '''Note:''' This is an irreversible operation.

  In general, it is recommended to create redirection pages instead of completely deleting an old page, as to not frustrate the visitor with broken links when coming to the site from a search engine. A redirection page is a short page that  contains a link such as  “See !SomeOtherPage”. However, deleting specific versions or even complete pages can make sense to remove spam or other abuse.

  ----
  See also: TracWiki, TracPermissions


name: TracChangeset
author: trac
ipnr: 127.0.0.1
text:
  = 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


name: TracEnvironment
author: trac
ipnr: 127.0.0.1
text:
  = 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


name: TracFastCgi
author: trac
ipnr: 127.0.0.1
text:
  = 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


name: WikiMacros
author: trac
ipnr: 127.0.0.1
text:
  =  Wiki Macros =
  Trac macros are plugins to extend the Trac engine with custom 'functions' written in Python. A macro inserts dynamic HTML data in any context supporting WikiFormatting.

  Another kind of macros are WikiProcessors. They typically deal with alternate markup formats and representation of larger blocks of information (like source code highlighting).

  == Using Macros ==
  Macro calls are enclosed in two ''square brackets''. Like python functions, macros can also have arguments, a comma separated list within parentheses. 

  === Examples ===

  {{{
   [[Timestamp]]
  }}}
  Display:
   [[Timestamp]]

  {{{
   [[HelloWorld(Testing)]]
  }}}
  Display:
   [[HelloWorld(Testing)]]

  == Available Macros ==

  ''Note that the following list will only contain the macro documentation if you've not enabled `-OO` optimizations, or not set the `PythonOptimize` option for [wiki:TracModPython mod_python].''

  [[MacroList]]

  == Macros from around the world ==
  The [http://projects.edgewall.com/trac/ Trac Project] has a section dedicated to user-contributed macros, [http://projects.edgewall.com/trac/wiki/MacroBazaar MacroBazaar]. If you're looking for new macros, or have written new ones to share with the world, don't hesitate adding it to the [http://projects.edgewall.com/trac/wiki/MacroBazaar MacroBazaar] wiki page.

  ----

  == Developing Custom Macros ==
  Macros, like Trac itself, are written in the [http://www.python.org/ Python programming language]. They are very simple modules, identified by the filename and should contain a single ''entry point'' function. Trac will display the returned data inserted into the HTML where the macro was called.

  It's easiest to learn from an example:
  {{{
  #!python
  # MyMacro.py -- The world's simplest macro

  def execute(hdf, args, env):
      return "Hello World called with args: %s" % args
  }}}

  You can also use the environment (`env`) object, for example to access configuration data and the database, for example:
  {{{
  #!python
  def execute(hdf, txt, env):
      return env.get_config('trac', 'repository_dir')
  }}}

  Note that since version 0.9, wiki macros can also be written as TracPlugins. This gives them some capabilities than “classic” macros do not have, such as directly access the HTTP request.

  For more information about developing macros, see the [http://projects.edgewall.com/trac/wiki/TracDev development resources] on the main project site.

  ----
  See also:  WikiProcessors, WikiFormatting, TracGuide


name: TracLogging
author: trac
ipnr: 127.0.0.1
text:
  = Trac Logging =
  [[TracGuideToc]]

  Trac supports logging of system messages using the standard [http://docs.python.org/lib/module-logging.html logging module] that comes with Python.

  Logging is configured in the {{{[logging]}}} section in [wiki:TracIni trac.ini].

  == Supported Logging Methods ==

  The log method is set using the `log_type` configuration option, which takes any of the following values:
   '''none'':: Suppress all log messages.
   '''file''':: Log messages to a file, specified with the `log_file` option in [wiki:TracIni trac.ini]. 
   '''stderr''':: Output all log entries to console ([wiki:TracStandalone tracd] only).
   '''syslog''':: (UNIX) Send messages to local syslogd via named pipe `/dev/log`.
   '''eventlog''':: (Windows) Use the system's NT eventlog for Trac logging.

  == Log Levels ==

  The verbosity level of logged messages can be set using the ''log_level'' directive in [wiki:TracIni trac.ini]. The log level defines the minimum level of urgency required for a message to be logged.

  The levels are:
   '''CRITICAL''':: Log only the most critical (typically fatal) errors.
   '''ERROR''':: Log failures, bugs and errors. 
   '''WARN''':: Log warnings, non-interrupting events.
   '''INFO''':: Diagnostic information, log information about all processing.
   '''DEBUG''':: Trace messages, profiling, etc.

  ----
  See also: TracIni, TracGuide, TracEnvironment


name: TracAccessibility
author: trac
ipnr: 127.0.0.1
text:
  = 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


name: TracTicketsCustomFields
author: trac
ipnr: 127.0.0.1
text:
  = Custom Ticket Fields =
  Trac supports adding custom, user-defined fields to the ticket module. Using custom fields, you can add typed, site-specific properties to tickets.

  == Configuration ==
  Configuring custom ticket fields is done in the [wiki:TracIni trac.ini] file. All field definitions should be under a section named `[ticket-custom]`.

  The syntax of each field definition is:
  {{{
   FIELD_NAME = TYPE
   (FIELD_NAME.OPTION = VALUE)
   ...
  }}}
  The example below should help to explain the syntax.

  === Available Field Types and Options ===
   * '''text''': A simple (one line) text field.
     * label: Descriptive label.
     * value: Default value.
     * order: Sort order placement. (Determines relative placement in forms.)
   * '''checkbox''': A boolean value check box.
     * label: Descriptive label.
     * value: Default value (0 or 1).
     * order: Sort order placement.
   * '''select''': Drop-down select box. Uses a list of values.
     * options: List of values, separated by '''|''' (vertical pipe).
     * value: Default value (Item #, starting at 0).
     * order: Sort order placement.
   * '''radio''': Radio buttons. Essentially the same as '''select'''.
     * label: Descriptive label.
     * options: List of values, separated by '''|''' (vertical pipe).
     * value: Default value (Item #, starting at 0).
     * order: Sort order placement.
   * '''textarea''': Multi-line text area.
     * label: Descriptive label.
     * value: Default text.
     * cols: Width in columns.
     * rows: Height in lines.
     * order: Sort order placement.

  === Sample Config ===
  {{{
  [ticket-custom]

  test_one = text
  test_one.label = Just a text box

  test_two = text
  test_two.label = Another text-box
  test_two.value = Just a default value

  test_three = checkbox
  test_three.label = Some checkbox
  test_three.value = 1

  test_four = select
  test_four.label = My selectbox
  test_four.options = one|two|third option|four
  test_four.value = 2

  test_five = radio
  test_five.label = Radio buttons are fun
  test_five.options = uno|dos|tres|cuatro|cinco
  test_five.value = 1

  test_six = textarea
  test_six.label = This is a large textarea
  test_six.value = Default text
  test_six.cols = 60
  test_six.rows = 30
  }}}

  ''Note: To make an entering an option for a `select` type field optional, specify a leading `|` in the `fieldname.options` option.''

  === Reports Involving Custom Fields ===

  The SQL required for TracReports to include custom ticket fields is relatively hard to get right. You need a `JOIN` with the `ticket_custom` field for every custom field that should be involved.

  The following example includes a custom ticket field named `progress` in the report:
  {{{
  #!sql
  SELECT p.value AS __color__,
     id AS ticket, summary, component, version, milestone, severity,
     (CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner,
     time AS created,
     changetime AS _changetime, description AS _description,
     reporter AS _reporter,
    (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress
    FROM ticket t
       LEFT OUTER JOIN ticket_custom c ON (t.id = c.ticket AND c.name = 'progress')
       JOIN enum p ON p.name = t.priority AND p.type='priority'
    WHERE status IN ('new', 'assigned', 'reopened')
    ORDER BY p.value, milestone, severity, time
  }}}

  Note in particular the `LEFT OUTER JOIN` statement here.

  ----
  See also: TracTickets, TracIni


name: WikiHtml
author: trac
ipnr: 127.0.0.1
text:
  = Using HTML in Wiki Text =

  Trac supports inserting HTML into any wiki context, accomplished using the HTML [wiki:WikiProcessors WikiProcessor].

  HTML support is built-in, and does not require installing any additional packages.

  == How to Use HTML ==
  To inform the wiki engine that a block of text should be treated as HTML, use the ''html'' processor. 

  This example should explain:
  {{{
  #!html
  <pre class="wiki">{{{
  #!html
  &lt;h1 style="text-align: right; color: blue"&gt;HTML Test&lt;/h1&gt;
  }}}</pre>
  }}}

  Results in:
  {{{
  #!html
  <h1 style="text-align: right; color: blue">HTML Test</h1>
  }}}

  == More Information ==

   * http://www.w3.org/ -- World Wide Web Consortium
   * http://www.w3.org/MarkUp/ -- HTML Markup Home Page

  ----
  See also:  WikiProcessors, WikiFormatting, WikiRestructuredText


name: WikiStart
author: trac
ipnr: 127.0.0.1
text:
  = Welcome to Trac 0.9.5 =

  Trac is a '''minimalistic''' approach to '''web-based''' management of
  '''software projects'''. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress.

  All aspects of Trac have been designed with the single goal to 
  '''help developers write great software''' while '''staying out of the way'''
  and imposing as little as possible on a team's established process and
  culture.

  As all Wiki pages, this page is editable, this means that you can
  modify the contents of this page simply by using your
  web-browser. Simply click on the "Edit this page" link at the bottom
  of the page. WikiFormatting will give you a detailed description of
  available Wiki formatting commands.

  "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created
  a new Trac environment, containing a default set of wiki pages and some sample
  data. This newly created environment also contains 
  [wiki:TracGuide documentation] to help you get started with your project.

  You can use [wiki:TracAdmin trac-admin] to configure
  [http://trac.edgewall.com/ Trac] to better fit your project, especially in
  regard to ''components'', ''versions'' and ''milestones''. 


  TracGuide is a good place to start.

  Enjoy! [[BR]]
  ''The Trac Team''

  == Starting Points ==

   * TracGuide --  Built-in Documentation
   * [http://projects.edgewall.com/trac/ The Trac project] -- Trac Open Source Project
   * [http://projects.edgewall.com/trac/wiki/TracFaq Trac FAQ] -- Frequently Asked Questions
   * TracSupport --  Trac Support

  For a complete list of local wiki pages, see TitleIndex.

  Trac is brought to you by [http://www.edgewall.com/ Edgewall Software],
  providing professional Linux and software development services to clients
  worldwide. Visit http://www.edgewall.com/ for more information.


name: WikiPageNames
author: trac
ipnr: 127.0.0.1
text:
  = Wiki Page Names =

  Wiki page names are written using CamelCase. Within a wiki text, any word in CamelCase automatically becomes a hyperlink to the wiki page with that same name.

  Page names must follow these rules:

   1. The name must consist of '''alphabetic characters only'''. No digits, spaces, punctuation, or underscores are allowed.
   1. A name must have at least two capital letters.
   1. The first character must be capitalized.
   1. Every capital letter must be followed by one or more lower-case letters. 
   1. The use of slash ( / ) is permitted to create a hierarchy inside the wiki.  (See !SubWiki and !ParentWiki macros in the [http://projects.edgewall.com/trac/wiki/MacroBazaar MacroBazaar] which provide a way to list all sub-entries and a link up the hierarchy respectively.)

  If you want to create a wiki page that doesn't follow CamelCase rules you could use the following syntax:
  {{{
  [wiki:Wiki_page]
  }}}

  This will be rendered as:
   [wiki:Wiki_page]

  ----
  See also: WikiNewPage, WikiFormatting, TracWiki


name: WikiRestructuredText
author: trac
ipnr: 127.0.0.1
text:
  = reStructuredText Support in Trac =

  Trac supports using ''reStructuredText'' (RST) as an alternative to wiki markup in any context WikiFormatting is used.

  From the reStucturedText webpage:
   "''reStructuredText is an easy-to-read, what-you-see-is-what-you-get plaintext markup syntax and parser   system. It is useful for in-line program documentation (such as Python docstrings), for quickly creating  simple web pages, and for standalone documents. reStructuredText is designed for extensibility for  specific application domains. ''"

  === Requirements ===
  Note that to activate RST support in Trac, the python docutils package must be installed. 
  If not already available on your operating system, you can download it at the [http://docutils.sourceforge.net/rst.html RST Website].

  === More information on RST ===

   * reStructuredText Website -- http://docutils.sourceforge.net/rst.html
   * RST Quick Reference -- http://docutils.sourceforge.net/docs/rst/quickref.html

  ----

  == Using RST in Trac ==
  To specify that a block of text should be parsed using RST, use the ''rst'' processor. 

  === TracLinks in reStructuredText ===

   * Trac provides a custom RST reference-directive 'trac' to allow TracLinks from within RST text.

   Example:
   {{{
   {{{
   #!rst
   This is a reference to |a ticket|

   .. |a ticket| trac:: #42
   }}}
   }}}

   For a complete example of all uses of the ''trac''-directive, please see WikiRestructuredTextLinks. 


   * Trac allows an even easier way of creating TracLinks in RST, using the custom '':trac:'' link naming scheme.

   Example:
   {{{
   {{{
   #!rst
   This is a reference to ticket `#12`:trac:

   To learn how to use Trac, see `TracGuide`:trac:
   }}}
   }}}

  === Syntax highlighting in reStructuredText ===

  There is a directive for doing TracSyntaxColoring in ReST as well. The directive is called
  code-block

  Example

  {{{
  {{{
  #!rst

  .. code-block:: python

   class Test:

      def TestFunction(self):
          pass

  }}}
  }}}

  Will result in the below.

  {{{
  #!rst

  .. code-block:: python

   class Test:

      def TestFunction(self):
          pass

  }}}

  === WikiMacros in reStructuredText ===

  For doing WikiMacros in ReST you use the same directive as for syntax highlightning i.e
  code-block. To work you must use a version of trac that has #801 applied. 

  === WikiMacro Example ===

  {{{
  {{{
  #!rst

  .. code-block:: HelloWorld
   
     Something I wanted to say


  }}}
  }}}

  Will result in the below.

  [[HelloWorld(Something I wanted to say)]]


  === Bigger ReST Example ===
  The example below should be mostly self-explanatory:
  {{{
  #!html
  <pre class="wiki">{{{
  #!rst
  FooBar Header
  =============
  reStructuredText is **nice**. It has its own webpage_.

  A table:

  =====  =====  ======
     Inputs     Output
  ------------  ------
    A      B    A or B
  =====  =====  ======
  False  False  False
  True   False  True
  False  True   True
  True   True   True
  =====  =====  ======

  RST TracLinks
  -------------

  See also ticket `#42`:trac:.

  .. _webpage: http://docutils.sourceforge.net/rst.html
  }}}</pre>
  }}}


  Results in:
  {{{
  #!rst
  FooBar Header
  =============
  reStructuredText is **nice**. It has its own webpage_.

  A table:

  =====  =====  ======
     Inputs     Output
  ------------  ------
    A      B    A or B
  =====  =====  ======
  False  False  False
  True   False  True
  False  True   True
  True   True   True
  =====  =====  ======

  RST TracLinks
  -------------

  See also ticket `#42`:trac:.

  .. _webpage: http://docutils.sourceforge.net/rst.html
  }}}


  ----
  See also: WikiRestructuredTextLinks, WikiProcessors, WikiFormatting


name: CamelCase
author: trac
ipnr: 127.0.0.1
text:
  = !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


name: TracTickets
author: trac
ipnr: 127.0.0.1
text:
  = The Trac Ticket System =
  [[TracGuideToc]]

  The Trac issue database provides simple but effective tracking of issues and bugs within a project.

  As the central project management element of Trac, tickets are used for '''project tasks''', '''feature requests''', '''bug reports''' and '''software support issues'''. 

  As with the TracWiki, this subsystem has been designed with the goal of making user contribution and participation as simple as possible. It should be as easy as possible to report bugs, ask questions and suggest improvements.

  An issue is assigned to a person who must resolve it or reassign the ticket to someone else.
  All tickets can be edited, annotated, assigned, prioritized and discussed at any time.

  '''Note:''' To make full use of the ticket system, use it as an ''in bucket'' for ideas and tasks for your project, rather than just bug/fault reporting. 

  == Ticket Fields ==

  A  ticket contains the following information attributes:
   
   * '''Reporter''' - The author of the ticket.
   * '''Type''' - The nature of the ticket (for example, defect or enhancement request)

   * '''Component''' - The project module or subsystem this ticket concerns.
   * '''Version''' - Version of the project that this ticket pertains to.
   * '''Keywords''' - Keywords that a ticket is marked with.  Useful for searching and report generation.

   * '''Priority''' - The importance of this issue, ranging from ''trivial'' to ''blocker''.
   * '''Milestone''' - When this issue should be resolved at the latest.
   * '''Assigned to/Owner''' - Principal person responsible for handling the issue.
   * '''Cc''' - A list of other associated people. ''Note that this does not imply responsiblity or any other policy.''
   
   * '''Resolution''' - Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}.
   * '''Status''' - What is the current status? One of {{{new}}}, {{{assigned}}}, {{{closed}}}, {{{reopened}}}.
   * '''Summary''' - A brief description summarizing the problem or issue.
   * '''Description''' - The body of the ticket. A good description should be specific, descriptive and to the point.

  '''Note:''' Versions of Trac prior to 0.9 did not have the ''type'' field, but instead provided a ''severity'' field and different default values for the ''priority'' field. This change was done to simplify the ticket model by removing the somewhat blurry distinction between ''priority'' and ''severity''. However, the old model is still available if you prefer it: just add/modify the default values of the ''priority'' and ''severity'', and optionally hide the ''type'' field by removing all the possible values through [wiki:TracAdmin trac-admin].


  == Changing and Commenting Tickets ==

  Once a ticket has been entered into Trac, you can at any time change the
  information by '''annotating''' the bug. This means changes and comments to
  the ticket are logged as a part of the ticket itself.

  When viewing a ticket, the history of changes will appear below the main ticket area.

  ''In the Trac project, we use ticket comments to discuss issues and tasks. This makes
  understanding the motivation behind a design- or implementation choice easier,
  when returning to it later.''

  '''Note:''' An important feature is being able to use TracLinks and
  WikiFormatting in ticket descriptions and comments. Use TracLinks to refer to
  other issues, changesets or files to make your ticket more specific and easier
  to understand.

  '''Note:''' See TracNotification for how to configure email notifications of ticket changes.

  === State Diagram ===
  http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020040607DF.png?format=raw


  == Default Values for Drop-Down Fields ==

  The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section:

   * `default_type`: Default ticket type
   * `default_component`: Name of the component selected by default
   * `default_version`: Name of the default version
   * `default_milestone`: Name of the default milestone
   * `default_priority`: Default priority value
   * `default_severity`: Default severity value

  If any of these options are omitted, the default value will either be the first in the list, or an empty value, depending on whether the field in question is required to be set.


  == Hiding Fields and Adding Custom Fields ==

  Many of the default ticket fields can be hidden from the ticket web interface simply by removing all the possible values through [wiki:TracAdmin trac-admin]. This of course only applies to drop-down fields, such as ''type'', ''priority'', ''severity'', ''component'', ''version'' and ''milestone''.

  Trac also lets you add your own custom ticket fields. See TracTicketsCustomFields for more information.


  == Assign-to as Drop-Down List ==

  If the list of possible ticket owners is finite, you can change the ''assign-to'' ticket field from a text input to a drop-down list. This is done by setting the `restrict_owner` option of the `[ticket]` section in [wiki:TracIni trac.ini] to “true”. In that case, Trac will use the list of all users who have logged in and set their email address to populate the drop-down field.

  ''Note that this feature is '''still experimental as of version 0.9'''. There is no way to only display a subset of all known users as possible ticket owners. Nor is there a convenient way to remove emeritus users short of directly modifying the database.''


  == Preset Values for New Tickets ==

  To create a link to the new-ticket form filled with preset values, you need to call the `/newticket?` URL with variable=value separated by &. 

  Possible variables are :

   * '''reporter''' - Name or email of the reporter
   * '''summary''' - Summary line for the ticket
   * '''description''' - Long description of the ticket
   * '''component''' - The component droplist
   * '''version''' - The version droplist
   * '''severity''' - The severity droplist
   * '''keywords''' - The keywords 
   * '''priority''' - The priority droplist
   * '''milestone''' - The milestone droplist
   * '''owner''' - The person responsible for the ticket
   * '''cc''' - The list of emails for notifying about the ticket change

  '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''


  See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification


name: TracSupport
author: trac
ipnr: 127.0.0.1
text:
  = Trac Support =

  Like in most [http://www.opensource.org/ open source projects], "free" Trac support is available primarily through the community itself, mainly through the [http://projects.edgewall.com/trac/wiki/MailingList mailing list] and the project wiki.

  There is also an [http://projects.edgewall.com/trac/wiki/IrcChannel IRC channel], where people might be able to help out. Much of the 'live' development discussions also happen there.

  Before you start a new support query, make sure you've done the appropriate searching:
   * in the project's [http://projects.edgewall.com/trac/wiki/TracFaq FAQ]
   * in past messages to the Trac [http://blog.gmane.org/gmane.comp.version-control.subversion.trac.general?set_user_css=http%3A%2F%2Fwww.edgewall.com%2Fcss%2Fgmane.css&do_set_user_css=t Mailing List]
   * in the Trac ticket system, using either a [http://projects.edgewall.com/trac/search?q=&ticket=on&wiki=on full search] or a [http://projects.edgewall.com/trac/query?summary=~&keywords=~" ticket query].

  ----
  See also: [http://projects.edgewall.com/trac/wiki/MailingList MailingList]


name: TracStandalone
author: trac
ipnr: 127.0.0.1
text:
  = Tracd =

  Tracd is a lightweight standalone Trac web server. In most cases it's easier to setup and runs faster than the [wiki:TracCgi CGI script].

  == Pros ==

   * Fewer dependencies: You don't need to install apache or any other web-server.
   * Fast: Should be as fast as the [wiki:TracModPython mod_python] version (and much faster than the [wiki:TracCgi CGI]).

  == Cons ==

   * Less features: Tracd implements a very simple web-server and is not as configurable as Apache HTTPD.
   * No native HTTPS support: [http://www.rickk.com/sslwrap/ sslwrap] can be used instead,
     or [http://lists.edgewall.com/archive/trac/2005-August/004381.html STUNNEL].

  == Usage examples ==

  A single project on port 8080. (http://localhost:8080/)
  {{{
   $ tracd -p 8080 /path/to/project
  }}}
  With more than one project. (http://localhost:8080/project1/ and http://localhost:8080/project2/)
  {{{
   $ tracd -p 8080 /path/to/project1 /path/to/project2
  }}}

  You can't have the last portion of the path identical between the projects since that's how trac keeps the URLs of the
  different projects unique. So if you use /project1/path/to and /project2/path/to, you will only see the second project.

  == Using Authentication ==

  Tracd provides support for both Basic and Digest authentication. The default is to use Digest; to use Basic authentication, replace `--auth` with `--basic-auth` in the examples below, and omit the realm.

  If the file `/path/to/users.htdigest` contain user accounts for project1 with the realm "mycompany.com", you'd use the following command-line to start tracd:
  {{{
   $ tracd -p 8080 --auth project1,/path/to/users.htdigest,mycompany.com /path/to/project1
  }}}
  ''Note that the project “name” passed to the `--auth` option is actually the base name of the project environment directory.""

  Of course, the digest file can be be shared so that it is used for more than one project:
  {{{
   $ tracd -p 8080 \
     --auth project1,/path/to/users.htdigest,mycompany.com \
     --auth project2,/path/to/users.htdigest,mycompany.com \
     /path/to/project1 /path/to/project2
  }}}

  == Generating Passwords Without Apache ==

  If you don't have Apache available, you can use this simple Python script to generate your passwords:

  {{{
  from optparse import OptionParser
  import md5

  # build the options
  usage = "usage: %prog [options]"
  parser = OptionParser(usage=usage)
  parser.add_option("-u", "--username",action="store", dest="username", type = "string",
                    help="the username for whom to generate a password")
  parser.add_option("-p", "--password",action="store", dest="password", type = "string",
                    help="the password to use")
  (options, args) = parser.parse_args()

  # check options
  if (options.username is None) or (options.password is None):
     parser.error("You must supply both the username and password")
     
  # Generate the string to enter into the htdigest file
  realm = 'trac'
  kd = lambda x: md5.md5(':'.join(x)).hexdigest()
  print ':'.join((options.username, realm, kd([options.username, realm, options.password])))
  }}}

  ----
  See also: TracInstall, TracCgi, TracModPython, TracGuide


name: TracInterfaceCustomization
author: trac
ipnr: 127.0.0.1
text:
  = Customizing the Trac Interface =
  [[TracGuideToc]]

  == Introduction ==
  This page is meant to give users suggestions on how they can customize the look of Trac.  Topics on this page cover editing the HTML templates and CSS files, but not the program code itself.  The topics are intended to show users how they can modify the look of Trac to meet their specific needs.  Suggestions for changes to Trac's interface applicable to all users should be filed as tickets, not listed on this page.

  == Project Logo and Icon ==
  The easiest parts of the Trac interface to customize are the logo and the site icon.  Both of these can be configured with settings in [wiki:TracIni trac.ini].

  The logo or icon image should be put in a folder named "htdocs" in your project's environment folder.  (''Note: in projects created with a Trac version prior to 0.9 you will need to create this folder'')

  Now configure the appropriate section of your [wiki:TracIni trac.ini]:

  === Logo ===
  Change the `src` setting to `site/` followed by the name of your image file.  The `width` and `height` settings should be modified to match your image's dimensions.

  {{{
  [header_logo]
  src = site/my_logo.gif
  alt = My Project
  width = 300
  height = 100
  }}}

  === Icon ===
  Icons should be a 16x16 image in `.gif` or `.ico` format.  Change the `icon` setting to `site/` followed by the name of your icon file.  Icons will typically be displayed by your web browser next to the site's URL and in the `Bookmarks` menu.

  {{{
  [project]
  icon = site/my_icon.ico
  }}}

  Note though that this icon is ignored by Internet Explorer, which only accepts a file named ``favicon.ico`` at the root of the host. To make the project icon work in both IE and other browsers, you can store the icon in the document root of the host, and reference it from ``trac.ini`` as follows:

  {{{
  [project]
  icon = /favicon.ico
  }}}

  == Site Header & Footer ==
  In the environment folder for each Trac project there should be a directory called {{{templates}}}.  This folder contains files {{{site_header.cs}}} and {{{site_footer.cs}}}.  Users can customize their Trac site by adding the required HTML markup to these files.  The content of these two files will be placed immediately following the opening {{{<body>}}} tag and immediately preceding the closing {{{</body>}}} tag of each page in the site, respectively.

  These files may contain static HTML, though if users desire to have dynamically generated content they can make use of the [http://www.clearsilver.net/ ClearSilver] templating language from within the pages as well. When you need to see what variables are available to the template, append the query string `?hdfdump=1` to the URL of your Trac site. This will display a structured view of the template data.

  == Site CSS ==
  The primary means to adjust the layout of a Trac site is by add [http://www.w3.org/TR/REC-CSS2/ CSS] style rules that overlay the default rules. This is best done by editing the `site_css.cs` file in the enviroment's `templates` directory. The content of that template gets inserted into a `<style type="text/css></style>` element on every HTML page generated by Trac.

  While you can add your custom style rules directory to the `site_css.cs` file, it is recommended that you simply reference an external style sheet, thereby enabling browsers to cache the CSS file instead of transmitting the rules with every response.

  The following example would import a style sheet located in the `style` root directory of your host:
  {{{
  @import url(/style/mytrac.css);
  }}}

  You can use a !ClearSilver variable to reference a style sheet stored in the project environment's `htdocs` directory:
  {{{
  @import url(<?cs var:chrome.href ?>/site/style.css);
  }}}

  == Main Templates ==

  It is also possible to use your own modified versions of the Trac [http://www.clearsilver.net/ ClearSilver] templates. Note though that this technique is not recommended because it makes upgrading Trac rather problematic: there are unfortunately several dependencies between the templates and the application code, such as the name of form fields and the structure of the template data, and these are likely to change between different versions of Trac.

  If you absolutely need to use modified templates, copy the template files from the default templates directory (usually in found in `$prefix/share/trac/templates`) into the `templates` directory of the project environment. Then modify those copies to get the desired results.


  ----
  See also TracGuide, TracIni


name: TracAdmin
author: trac
ipnr: 127.0.0.1
text:
  = 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


name: SandBox
author: trac
ipnr: 127.0.0.1
text:
  = The Sandbox =

  This is just a page to practice and learn WikiFormatting. 

  Go ahead, edit it freely.


name: TracGuide
author: trac
ipnr: 127.0.0.1
text:
  = 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.


name: TracLinks
author: trac
ipnr: 127.0.0.1
text:
  = Trac Links =
  As you might have guessed, TracLinks are a very fundamental feature of Trac.

  They allow hyperlinking between Trac entities (tickets, reports, changesets, Wiki
  pages, milestones and source files) from anywhere WikiFormatting is used.

  TracLinks are generally of the form '''type:id''' (where ''id'' represents the
  number, name or path of the item) though some frequently used kinds of items
  also have short-hand notations.

  Some examples:
   * Tickets: '''!#1''' or '''!ticket:1'''
   * Reports: '''!{1}''' or '''!report:1'''
   * Changesets: '''!r1''', '''![1]''' or '''!changeset:1'''
   * Revision log: '''!r1:3''', '''![1:3]''' or '''!log:#1:3'''
   * Wiki pages: '''CamelCase''' or '''!wiki:CamelCase'''
   * Milestones: '''!milestone:1.0'''
   * Attachment: '''!attachment:ticket:944:attachment.1073.diff'''
   * Files: '''!source:trunk/COPYING'''
   * A specific file revision: '''!source:/trunk/COPYING#200'''
  Display:
   * Tickets: #1 or ticket:1
   * Reports: {1} or report:1
   * Changesets: r1, [1] or changeset:1
   * Differences: r1:3, [1:3] or log:#1:3
   * Wiki pages: CamelCase or wiki:CamelCase
   * Milestones: milestone:1.0
   * Files: source:trunk/COPYING
   * Attachment: attachment:ticket:944:attachment.1073.diff
   * A specific file revision: source:/trunk/COPYING#200

  '''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to
  pages whose names do not follow WikiPageNames rules, i.e., single words,
  non-alphabetic characters, etc.

  Trac links using the full (non-shorthand) notation can also be given a custom
  link title like this:

  {{{
  [ticket:1 This is a link to ticket number one].
  }}}

  Display: [ticket:1 This is a link to ticket number one].

  If the title is be omitted, only the id (the part after the colon) is displayed:

  {{{
  [ticket:1]
  }}}

  Display: [ticket:1]

  It might seem a simple enough concept at a glance, but actually allows quite a complex network of information. In practice, it's very intuitive and simple to use, and we've found the "link trail" extremely helpful to better understand what's happening in a project or why a particular change was made.

  == attachement: links ==

  The link syntax for attachments is as follows:
   * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object
   * !attachment:wiki:MyPage:the_file.txt creates a link to the attachment the_file.txt of the !MyPage wiki page
   * !attachment:ticket:753:the_file.txt creates a link to the attachment the_file.txt of the ticket 753 !attachment:wiki:MyPage:the_file.txt

  == source: links ==

  The default behavior for a source:/some/path link is to open the directory browser 
  if the path points to a directory and otherwise open the log view. 
  It's also possible to link directly to a specific revision of a file like this: source:/some/file@123 
  or like this to link to the latest revision: source:/some/file@latest.
  If the revision is specified, one can even link to a specific line number: !source:/some/file@123#L10 
  [[comment(TODO: remove the ! when Edgewall Trac is upgraded with the support for the line syntax)]]

  == Quoting space in TracLinks ==

  The usual syntax for quoting space is:

   * !attachment:'the file.txt' or
   * !attachment:"the file.txt" 

  == Where to use TracLinks ==
  You can use TracLinks in:

   * Source code (Subversion) commit messages
   * Wiki pages
   * Full descriptions for tickets, reports and milestones

  and any other text fields explicitly marked as supporting WikiFormatting.

  == Escaping Links ==

  To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
  {{{
   !NoLinkHere.
   ![42] is not a link either.
  }}}

  Display:
   !NoLinkHere.
   ![42] is not a link either.

  ----
  See also: WikiFormatting, TracWiki
   


name: TracQuery
author: trac
ipnr: 127.0.0.1
text:
  = Trac Ticket Queries =
  [[TracGuideToc]]

  In addition to [wiki:TracReports reports], Trac provides support for ''custom ticket queries'', used to display lists of tickets meeting a specified set of criteria. 

  To configure and execute a custom query, switch to the ''View Tickets'' module from the navigation bar, and select the ''Custom Query'' link.

  == Filters ==
  When you first go to the query page the default filters will display all open tickets, or if you're logged in it will display open tickets assigned to you.  Current filters can be removed by clicking the button to the right with the minus sign on the label.  New filters are added from the pulldown list in the bottom-right corner of the filters box.  Filters with either a text box or a pulldown menu of options can be added multiple times to perform an ''or'' of the criteria.

  You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket.

  Once you've edited your filters click the ''Update'' button to refresh your results.

  == Navigating Tickets ==
  Clicking on one of the query results will take you to that ticket.  You can navigate through the results by clicking the ''Next Ticket'' or ''Previous Ticket'' links just below the main menu bar, or click the ''Back to Query'' link to return to the query page.  

  You can safely edit any of the tickets and continue to navigate through the results using the ''Next/Previous/Back to Query'' links after saving your results.  When you return to the query any tickets you edited will be displayed with italicized text.  If one of the tickets was edited such that it no longer matches the query criteria the text will also be greyed.  The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again.

  == Saving Queries ==

  While Trac does not yet allow saving a named query and somehow making it available in a navigable list, you can save references to queries in Wiki content, as described below.

  === Using TracLinks ===

  You may want to save some queries so that you can come back to them later.  You can do this by making a link to the query from any Wiki page.
  {{{
  [query:status=new|assigned|reopened&version=0.8 Active tickets against 0.8]
  }}}

  Which is displayed as:
    [query:status=new|assigned|reopened&version=0.8 Active tickets against 0.8]

  This uses a very simple query language to specify the criteria (see [wiki:TracQuery#QueryLanguage Query Language]).

  Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading `?` character:
  {{{
  [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
  }}}

  Whis is displayed as:
    [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]

  The advantage of this approach is that you can also specify the grouping and ordering, which is not possible using the first syntax.

  === Using the `[[TicketQuery]]` Macro ===

  The `[[TicketQuery]]` macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.

  Example:
  {{{
  [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate)]]
  }}}

  This is displayed as:
    [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate)]]

  Just like the [wiki:TracQuery#UsingTracLinks query: wiki links], the parameter of this macro expects a query string formatted according to the rules of the simple [wiki:TracQuery#QueryLanguage ticket query language].

  A more compact representation without the ticket summaries is also available:
  {{{
  [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate, compact)]]
  }}}

  This is displayed as:
    [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate, compact)]]

  === Query Language ===

  `query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Basically, the filters are separate by ampersands (`&`). Each filter then consists of the ticket field name, an operator, and one or more values. More than one value are separated by a pipe (`|`), meaning that the filter matches any of the values.

  The available operators are:
  || '''=''' || the field content exactly matches the one of the values ||
  || '''~=''' || the field content contains one or more of the values ||
  || '''!^=''' || the field content starts with one of the values ||
  || '''$=''' || the field content ends with one of the values ||

  All of these operators can also be negated:
  || '''!=''' || the field content matches none of the values ||
  || '''!~=''' || the field content does not contain any of the values ||
  || '''!!^=''' || the field content does not start with any of the values ||
  || '''!$=''' || the field content does not end with any of the values ||

  ----
  See also: TracTickets, TracReports, TracGuide


name: TracUnicode
author: trac
ipnr: 127.0.0.1
text:
  = Unicode Support in Trac =
  Trac stores all text using UTF-8 encoding, including text in tickets and wiki pages. 

  As such, it supports most (all?) commonly used character encodings.


  == Examples ==
  Please keep sorted order when you add an entry.

  === Arabic ===
  تراك يقوم بحفظ كل الكلمات باستخدام صيغة UTF-8، بما في ذلك الكلمات المستخدمة في صفحات  التيكت والويكي.

  === Bulgarian ===
  Българският език работи ли?

  === Česky ===
  Čeština v kódování UTF-8, žádný problém.

  === Chinese ===
  Traditional: ''繁體中文, 許功蓋會育''; Simplified: ''简体中文，许功盖会育''

  === English ===
  Yes indeed, Trac supports English. Fully.

  === Français ===
  ''Il est possible d'écrire en Français : à, ç, û, ...''

  === German ===
  Trac-Wiki muß auch deutsche Umlaute richtig anzeigen: ö, ä, ü, ...

  === Greek ===
  Τα Ελληνικά υποστηρίζονται επαρκώς επίσης.

  === Hebrew ===
  אני יכול לאכול זכוכית וזה לא מזיק לי

  === Icelandic ===
  ''Ævar sagði við ömmu sína: Sjáðu hvað ég er stór!''

  === Japanese ===
  ''漢字 ひらがな カタカナ ﾊﾝｶｸｶﾅ''

  === Korean ===
  ''이번에는 한글로 써보겠습니다. 잘 보이나요?''

  === Persian (Farsi) ===
  این یک متن فارسی است ولی از چپ به راست

  === Polish ===
  Pchnąć w tę łódź jeża lub ośm skrzyń fig

  === Portuguese ===
  É possível guardar caracteres especias da língua portuguesa, incluindo o símbolo da moeda européia '€', trema 'ü', crase 'à', agudos 'áéíóú', circunflexos 'âêô', til 'ãõ', cedilha 'ç', ordinais 'ªº', grau '°¹²³'.

  === Russian ===
  Проверка русского языка: кажется работает...

  === Serbian ===
  Podržan, uprkos činjenici da se za njegovo pisanje koriste чак два алфабета.

  === Slovenian ===
  Ta suhi škafec pušča vodo že od nekdaj!

  === Spanish ===
  Esto es un pequeño texto en Español, ahora una con acentó

  === Swedish ===
  ''Räven raskar över isen med luva på.''

  === Thai ===
  Trac แสดงภาษาไทยได้อย่างถูกต้อง!

  === Ukrainian ===
  Перевірка української мови...


name: TracUpgrade
author: trac
ipnr: 127.0.0.1
text:
  = Upgrade Instructions =
  [[TracGuideToc]]

  A Trac environment sometimes needs to be upgraded before it can be used with a new version of Trac. This document describes the steps necessary to upgrade an environment.

   '''Note''': ''Environment upgrades are not necessary for minor version releases unless otherwise noted. For example, there's no need to upgrade a Trac environment created with (or upgraded) 0.8.0 when installing 0.8.4 (or any other 0.8.x release).''

  == General Instructions ==

  Typically, there are four steps involved in upgrading to a newer version of Trac:

  === Update the Trac Code ===

  Get the new version of Trac, either by downloading an offical release package or by checking it out from the [http://projects.edgewall.com/trac/wiki/SubversionRepository Subversion repository].

  If you have a source distribution, you need to run
  {{{
  python setup.py install
  }}}

  to install the new version. If you've downloaded the Windows installer, you execute it, and so on.

  In any case, if you're doing a major version upgrade (such as from 0.8 to 0.9), it is ''highly'' recommended that you first remove the existing Trac code. To do this, you need to delete the `trac` directory from the Python `lib/site-packages` directory. You may also want to remove the Trac `cgi-bin`, `htdocs` and `templates` directories that are commonly found in a directory called `share/trac` (the exact location depends on your platform).

  === Upgrade the Trac Environment ===

  Unless noted otherwise, upgrading between major versions (such as 0.8 and 0.9) involves changes to the database schema, and possibly the layout of the [wiki:TracEnvironment environment directory]. Fortunately, Trac provides automated upgrade scripts to ease the pain. These scripts are run via [wiki:TracAdmin trac-admin]:
  {{{
  trac-admin /path/to/projenv upgrade
  }}}

  This command will do nothing if the environment is already up-to-date.

  Note that if you are using a PostgreSQL database, this command will fail with the message that the environment can only be backed up when you use an SQLite database. This means that you will have to backup the repository and the database manually. Then, to perform the actual upgrade, run:
  {{{
  trac-admin /path/to/projenv upgrade --no-backup
  }}}

  === Update the Trac Documentation ===

  Every [wiki:TracEnvironment Trac environment] includes a copy of the Trac documentation for the installed version. As you probably want to keep the included documentation in sync with the installed version of Trac, [wiki:TracAdmin trac-admin] provides a command to upgrade the documentation:
  {{{
  trac-admin /path/to/projenv wiki upgrade
  }}}

  Note that this procedure will of course leave your `WikiStart` page intact.

  === Restart the Web Server ===

  In order to reload the new Trac code you will need to restart your web server (note this is not necessary for [wiki:TracCgi CGI]).

  == Specific Versions ==

  The following sections discuss any extra actions that may need to be taken to upgrade to specific versions of Trac.

  == From 0.9-beta to 0.9 ==

  If inclusion of the static resources (style sheets, javascript, images) is not working, check the value of the `htdocs_location` in trac.ini. For [wiki:TracModPython mod_python], [wiki:TracStandalone Tracd] and [wiki:TracFastCgi FastCGI], you can simply remove the option altogether. For [wiki:TracCgi CGI], you should fix it to point to the URL you mapped the Trac `htdocs` directory to (although you can also remove it and then [wiki:TracCgi#MappingStaticResources map the static resources]). If you're still having problems after removing the option, check the paths in the `trac/siteconfig.py` file and fix them if they're incorrect.

  If you've been using plugins with a beta release of Trac 0.9, or have disabled some of the built-in components, you might have to update the rules for disabling/enabling components in [wiki:TracIni trac.ini]. In particular, globally installed plugins now need to be enabled explicitly. See TracPlugins and TracIni for more information.

  If you want to enable the display of all ticket changes in the timeline (the “Ticket Details” option), you now have to explicitly enable that in [wiki:TracIni trac.ini], too:

  {{{
  [timeline]
  ticket_show_details = true
  }}}

  == From 0.8.x to 0.9 ==

  [wiki:TracModPython mod_python] users will also need to change the name of the mod_python handler in the Apache HTTPD configuration:
  {{{
     from: PythonHandler trac.ModPythonHandler
     to:   PythonHandler trac.web.modpython_frontend
  }}}

  If you have [http://initd.org/tracker/pysqlite PySQLite] 2.x installed, Trac will now try to open your SQLite database using the SQLite 3.x file format. The database formats used by SQLite 2.8.x and SQLite 3.x are incompatible. If you get an error like ''“file is encrypted or is not a database”'' after upgrading, then you must convert your database file.

  To do this, you need to have both SQLite 2.8.x and SQLite 3.x installed (they have different filenames so can coexist on the same system). Then use the following commands:
  {{{
   $ mv trac.db trac2.db
   $ sqlite trac2.db .dump | sqlite3 trac.db
  }}}

  After testing that the conversion was successful, the `trac2.db` file can be deleted. For more information on the SQLite upgrade see http://www.sqlite.org/version3.html.

  == From 0.7.x to 0.8 ==

  0.8 adds a new roadmap feature which requires additional permissions. While a
  fresh installation will by default grant ROADMAP_VIEW and MILESTONE_VIEW
  permissions to anonymous, these permissions have to be granted manually when
  upgrading:
  {{{
   $ trac-admin /path/to/projectenv permission add anonymous MILESTONE_VIEW
   $ trac-admin /path/to/projectenv permission add anonymous ROADMAP_VIEW
  }}}

  -----
  See also: TracGuide, TracInstall


name: WikiNewPage
author: trac
ipnr: 127.0.0.1
text:
  = Steps to Add a New Wiki Page =

   1. Choose a name for your new page. See WikiPageNames for naming conventions.
   1. Edit an existing page and add a hyperlink to your new page. Save your changes.
   1. Follow the link you created to take you to the new page. Trac will display a "describe !PageName here" message.
   1. Click the "Edit this page" button to edit and add content to your new page. Save your changes.
   1. All done. Your new page is published.


  See also: TracWiki, WikiFormatting, TracLinks, WikiDeletePage 


name: TracWiki
author: trac
ipnr: 127.0.0.1
text:
  = The Trac Wiki Engine =
  [[TracGuideToc]]

  Trac has a built-in wiki engine, used for text and documentation throughout the system. WikiFormatting is used in [wiki:TitleIndex wiki pages], [wiki:TracTickets tickets] and [wiki:TracChangeset check-in log messages].  This allows for formatted text and hyperlinks in and between all Trac modules.

  Editing wiki text is easy, using any web browser and a simple formatting system (see WikiFormatting), rather than more complex markup languages like HTML.  The reasoning behind its design is that HTML, with its large collection of nestable tags, is too complicated to allow fast-paced editing, and distracts from the actual content of the pages. Note though that Trac also supports [wiki:WikiHtml HTML] and [wiki:WikiRestructuredText reStructuredText] as alternative markup formats.

  The main goal of the wiki is making editing text easier and ''encourage'' people to contribute and annotate text content for a project. 

  The wiki itself does not enforce any structure, but rather resembles a stack of empty paper sheets, where you can organize information and documentation as you see fit, and later reorganize if necessary. 

  For more help on editing wiki text, see:
   * WikiFormatting
   * WikiPageNames
   * WikiNewPage
   * TracLinks
   * WikiMacros
   * WikiProcessors

  If you want to practice editing, please use the SandBox.

  Some more information about wiki on the web:
   * http://wikipedia.org/wiki/Wiki
   * http://c2.com/cgi/wiki?WikiHistory
   * http://www.usemod.com/cgi-bin/mb.pl?WhyWikiWorks


name: TracBackup
author: trac
ipnr: 127.0.0.1
text:
  = 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


name: TracPermissions
author: trac
ipnr: 127.0.0.1
text:
  = Trac Permissions =
  [[TracGuideToc]]

  Trac uses a simple but flexible permission system to control what users can and can't access.

  Permission privileges are managed using the [wiki:TracAdmin trac-admin] tool.

  Regular visitors, non-authenticated users, accessing the system are assigned the default 
  role (''user'') named {{{anonymous}}}. 
  Assign permissions to the {{{anonymous}}} user to set privileges for non-authenticated/guest users.

  In addition to these privileges users can be granted additional individual 
  rights in effect when authenticated and logged into the system.

  == Available Privileges ==

  To enable all privileges for a user, use the `TRAC_ADMIN` permission. Having `TRAC_ADMIN` is like being `root` on a *NIX system, it will let you do anything you want.

  Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac:

  === Repository Browser ===

  || `BROWSER_VIEW` || View directory listings in the [wiki:TracBrowser repository browser] ||
  || `LOG_VIEW` || View revision logs of files and directories in the [wiki:TracBrowser repository browser] ||
  || `FILE_VIEW` || View files in the [wiki:TracBrowser repository browser] ||
  || `CHANGESET_VIEW` || View [wiki:TracChangeset repository check-ins] ||

  === Ticket System ===

  || `TICKET_VIEW` || View existing [wiki:TracTickets tickets] and perform [wiki:TracQuery ticket queries] ||
  || `TICKET_CREATE` || Create new [wiki:TracTickets tickets] ||
  || `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] ||
  || `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties ||
  || `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets] ||
  || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments. ||

  === Roadmap ===

  || `MILESTONE_VIEW` || View a milestone ||
  || `MILESTONE_CREATE` || Create a new milestone ||
  || `MILESTONE_MODIFY` || Modify existing milestones ||
  || `MILESTONE_DELETE` || Delete milestones ||
  || `MILESTONE_ADMIN` || All `MILESTONE_*` permissions ||
  || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page ||
  || `ROADMAP_ADMIN` || Alias for `MILESTONE_ADMIN` (deprecated) ||

  === Reports ===

  || `REPORT_VIEW` || View [wiki:TracReports reports] ||
  || `REPORT_SQL_VIEW` || View the underlying SQL query of a [wiki:TracReports report] ||
  || `REPORT_CREATE` || Create new [wiki:TracReports reports] ||
  || `REPORT_MODIFY` || Modify existing [wiki:TracReports reports] ||
  || `REPORT_DELETE` || Delete [wiki:TracReports reports] ||
  || `REPORT_ADMIN` || All `REPORT_*` permissions ||

  === Wiki System ===

  || `WIKI_VIEW` || View existing [wiki:TracWiki wiki] pages ||
  || `WIKI_CREATE` || Create new [wiki:TracWiki wiki] pages ||
  || `WIKI_MODIFY` || Change [wiki:TracWiki wiki] pages ||
  || `WIKI_DELETE` || Delete [wiki:TracWiki wiki] pages and attachments ||
  || `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. ||

  === Others ===

  || `TIMELINE_VIEW` || View the [wiki:TracTimeline timeline] page ||
  || `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries ||
  || `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins ||

  == Granting Privileges ==

  Currently the only way to grant privileges to users is by using the `trac-admin` script. The current set of privileges can be listed with the following command:
  {{{
    $ trac-admin /path/to/projenv permission list
  }}}

  This command will allow the user ''bob'' to delete reports:
  {{{
    $ trac-admin /path/to/projenv permission add bob REPORT_DELETE
  }}}

  == Permission Groups ==

  Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc.
  {{{
    $ trac-admin /path/to/projenv permission add developer WIKI_ADMIN
    $ trac-admin /path/to/projenv permission add developer REPORT_ADMIN
    $ trac-admin /path/to/projenv permission add developer TICKET_MODIFY
    $ trac-admin /path/to/projenv permission add bob developer
    $ trac-admin /path/to/projenv permission add john developer
  }}}

  == Default Permissions ==

  Granting privileges to the special user ''anonymous'' can be used to control what an anonymous user can do before they have logged in.

  In the same way, privileges granted to the special user ''authenticated'' will apply to any authenticated (logged in) user.

  ----
  See also: TracAdmin, TracGuide


name: TracImport
author: trac
ipnr: 127.0.0.1
text:
  = 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.


name: TracInstall
author: trac
ipnr: 127.0.0.1
text:
  = Trac Installation Guide = 
  [[TracGuideToc]]

  Trac is a lightweight project management tool that is implemented as a web-based application. Trac is written in the Python programming language and can use [http://sqlite.org/ SQLite] or [http://www.postgresql.org/ PostgreSQL] as  database. For HTML rendering, Trac uses the [http://www.clearsilver.net/ Clearsilver] templating system.

  What follows are generic instructions for installing and setting up Trac and its requirements. While you can find instructions for installing Trac on specific systems at [http://projects.edgewall.com/trac/wiki/TracInstallPlatforms TracInstallPlatforms] on the main Trac site, please be sure to first read through these general instructions to get a good understanding of the tasks involved.

  == Requirements ==

  To install Trac, the following software packages must be installed:

   * [http://www.python.org/ Python], version >= 2.3.
     * Python 2.4 is not supported on Windows since there are no Subversion bindings available for it.
     * For RPM-based systems you might also need the `python-devel` and `python-xml` packages.
   * [http://subversion.tigris.org/ Subversion], version >= 1.0. (>= 1.1 recommended) and corresponding [http://svnbook.red-bean.com/svnbook-1.1/ch08s02.html#svn-ch-8-sect-2.3 Python bindings]
     * Trac uses the [http://www.swig.org/ SWIG] bindings included in the Subversion distribution, '''not''' [http://pysvn.tigris.org/ PySVN] (which is sometimes confused with the standard SWIG bindings).
     * If Subversion was already installed without the SWIG bindings, you'll need to re-`configure` Subversion and `make swig-py`, `make install-swig-py`.
   * [http://www.clearsilver.net/ ClearSilver], version >= 0.9.3
     * With python-bindings (`./configure --with-python=/usr/bin/python`)

  === For SQLite ===

   * [http://www.sqlite.org/ SQLite], version 2.8.x or 3.x
   * [http://pysqlite.org/ PySQLite]
     * version 1.0.x (for SQLite 2.8.x)
     * version 1.1.x or 2.x (for SQLite 3.x)

  === For PostgreSQL ===

   * [http://www.postgresql.org/ PostgreSQL]
   * [http://initd.org/projects/psycopg1 psycopg1], [http://initd.org/projects/psycopg2 psycopg2], or [http://pypgsql.sourceforge.net/ pyPgSQL]

  === Optional Requirements ===

   * A CGI-capable web server (see TracCgi), or
   * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi), or
   * [http://httpd.apache.org/ Apache] with [http://www.modpython.org/ mod_python 3.1.3+] (see TracModPython)
   * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.5a13 for using plugins (see TracPlugins)
   * [http://docutils.sourceforge.net/ docutils], version >= 0.3.3 for WikiRestructuredText.
   * [http://silvercity.sourceforge.net/ SilverCity] and/or [http://www.gnu.org/software/enscript/enscript.html Enscript] for [wiki:TracSyntaxColoring syntax highlighting].

  '''Attention''': The various available versions of these dependencies are not necessarily interchangable, so please pay attention to the version numbers above. If you are having trouble getting Trac to work please double-check all the dependencies before asking for help on the [http://projects.edgewall.com/trac/wiki/MailingList MailingList] or [http://projects.edgewall.com/trac/wiki/IrcChannel IrcChannel].

  Please refer to the documentation of these packages to find out how they are best installed. In addition, most of the [http://projects.edgewall.com/trac/wiki/TracInstallPlatforms platform-specific instructions] also describe the installation of the dependencies.

  == Installing Trac ==

  Like most Python programs, the Trac Python package is installed by running the following command at the top of the source directory:
  {{{
  $ python ./setup.py install
  }}}

  ''Note: you'll need root permissions or equivalent for this step.''

  This will byte-compile the python source code and install it in the `site-packages` directory
  of your Python installation. The directories `cgi-bin`, `templates`, `htdocs`, `wiki-default` and `wiki-macros` are all copied to `$prefix/share/trac/.`

  The script will also install the [wiki:TracAdmin trac-admin] command-line tool, used to create and maintain [wiki:TracEnvironment project environments], as well as the [wiki:TracStandalone tracd] standalone server.

  === Advanced Users ===

  To install Trac to a custom location, or find out about other advanced installation options, run:
  {{{
  $ python ./setup.py --help
  }}}

  Specifically, you might be interested in:
  {{{
  $ python ./setup.py install --prefix=/path/you/want
  }}}


  == Creating a Project Environment ==

  A [wiki:TracEnvironment Trac environment] is the backend storage where Trac stores information like wiki pages, tickets, reports, settings, etc. An environment is basically a directory that contains a human-readable configuration file and various other files and directories.

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

  [wiki:TracAdmin trac-admin] will prompt you for the information it needs to create the environment, such as the name of the project, the path to an existing subversion repository, the [wiki:TracEnvironment#DatabaseConnectionStrings database connection string], and so on. If you're not sure what to specify for one of these options, just leave it blank to use the default value. The database connection string in particular will always work as long as you have SQLite installed. The only option where the default value is likely to not work is the path to the Subversion repository, so make sure that one's correct.

  Also note that the values you specify here can be changed later by directly editing the [wiki:TracIni] configuration file.

  ''Note: The user account under which the web server runs will require write permissions to the environment
  directory and all the files inside.''


  == Running the Standalone Server ==

  After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]:
  {{{
  $ tracd --port 8000 /path/to/projectenv
  }}}

  Then, fire up a browser and visit `http://localhost:8000/`. You should get a simple listing of all environments that tracd knows about. Follow the link to the environment you just created, and you should see Trac in action.


  == Running Trac on a Web Server ==

  Trac provides three options for connecting to a “real” web server: [wiki:TracCgi CGI], [wiki:TracFastCgi FastCGI] and [wiki:TracModPython mod_python]. For decent performance, it is recommended that you use either FastCGI or mod_python.

  == Configuring Authentication ==

  The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac.  To learn about how to accomplish these tasks, please visit one of the following pages:

   * TracStandalone if you use the standalone server, `tracd`.
   * TracCgi if you use the CGI or FastCGI methods.
   * TracModPython if you use the mod_python method.

  == Using Trac ==

  Once you have your Trac site up and running, you should be able to browse your subversion repository, create tickets, view the timeline, etc.

  Keep in mind that anonymous (not logged in) users can by default access most but not all of the features. You will need to configure authentication and grant additional [wiki:TracPermissions permissions] to authenticated users to see the full set of features.

  ''Enjoy!''

  [http://projects.edgewall.com/trac/wiki/TracTeam The Trac Team]

  ----
  See also:  TracGuide, TracCgi, TracFastCgi, TracModPython, TracUpgrade, TracPermissions


name: TracPlugins
author: trac
ipnr: 127.0.0.1
text:
  = Trac Plugins =
  [[TracGuideToc]]

  Since version 0.9, Trac supports plugins that extend the built-in functionality. The plugin functionality is based on the [http://projects.edgewall.com/trac/wiki/TracDev/ComponentArchitecture component architecture].

  == Requirements ==

  To use plugins in Trac, you need to have [http://peak.telecommunity.com/DevCenter/setuptools setuptools] (version 0.6) installed.

  To install `setuptools`, download the bootstrap module [http://peak.telecommunity.com/dist/ez_setup.py ez_setup.py] and execute it as follows:
  {{{
  $ python ez_setup.py
  }}}

  If the `ez_setup.py` script fails to install the setuptools release, you can download it from [http://www.python.org/pypi/setuptools PyPI] and install it manually.

  == Installing a Trac Plugin ==

  === For a Single Project ===

  Plugins are packaged as [http://peak.telecommunity.com/DevCenter/PythonEggs Python eggs]. That means they are ZIP archives with the file extension `.egg`. If you have downloaded a source distribution of a plugin, you can run:
  {{{
  $ python setup.py bdist_egg
  }}}
  to build the `.egg` file.

  Once you have the plugin archive, you need to copy it into the `plugins` directory of the [wiki:TracEnvironment project environment]. Also, make sure that the web server has sufficient permissions to read the plugin egg.

  === For All Projects ===

  Plugins that you want to use in all your projects (such as [http://projects.edgewall.com/trac/wiki/WebAdmin WebAdmin]) can be installed globally by running:
  {{{
  $ python setup.py install
  }}}

  Alternatively, you can just drop the `.egg` file in the Python `site-packages` directory.

  Unlike plugins installed per-environment, you'll have to explicitly enable globally installed plugins via [wiki:TracIni trac.ini]. This is done in the `[components]` section of the configuration file, for example:
  {{{
  [components]
  webadmin.* = enabled
  }}}

  The name of the option is the Python package of the plugin. This should be specified in the documentation of the Plugin, but can also be easily find out by looking at the source (look for a top-level directory that contains a file named `__init__.py`.)

  == Setting up the Plugin Cache ==

  Some plugins will need to be extracted by the Python eggs runtime (`pkg_resources`), so that their contents are actual files on the file system. The directory in which they are extracted defaults to the home directory of the current user, which may or may not be a problem. You can however override the default location using the `PYTHON_EGG_CACHE` environment variable.

  To do this from the Apache configuration, use the `SetEnv` directive as follows:
  {{{
  SetEnv PYTHON_EGG_CACHE /path/to/dir
  }}}

  This works whether your using the [wiki:TracCgi CGI] or the [wiki:TracModPython mod_python] front-end. Put this directive next to where you set the path to the [wiki:TracEnvironment Trac environment], i.e. in the same `<Location>` block.

  For example (for CGI):
  {{{
   <Location /trac>
     SetEnv TRAC_ENV /path/to/projenv
     SetEnv PYTHON_EGG_CACHE /path/to/dir
   </Location>
  }}}

  or (for mod_python):
  {{{
   <Location /trac>
     SetHandler mod_python
     ...
     SetEnv PYTHON_EGG_CACHE /path/to/dir
   </Location>
  }}}

  For [wiki:TracFastCgi FastCGI], you'll need to `-initial-env` option, or whatever is provided by your web server for setting environment variables.

  ----
  See also TracGuide, [http://projects.edgewall.com/trac/wiki/PluginList plugin list], [http://projects.edgewall.com/trac/wiki/TracDev/ComponentArchitecture component architecture]


name: TracSyntaxColoring
author: trac
ipnr: 127.0.0.1
text:
  = Syntax Coloring of Source Code =
  Trac supports language-specific syntax highlighting of source code in [wiki:WikiFormatting wiki formatted] text and the [wiki:TracBrowser repository browser].

  To do this, Trac uses external libraries with support for a great number of programming languages.

  Currently Trac supports syntax coloring using one or more of the following packages:

   * [http://people.ssh.fi/mtr/genscript/ GNU Enscript]
   * [http://silvercity.sourceforge.net/ SilverCity]

  To activate syntax coloring, simply install either one (or more) of these packages. No additional configuration is required, however to modify the colors, have a look at `trac/htdocs/css/code.css`.

  When in use, Trac will automatically prioritize !SilverCity highlighting over Enscript if possible, (see note below). 

  If neither package is available, Trac will display the data as plain text. 

  '''Note:''' Enscript supports a greater number of languages, however !SilverCity is generally faster since it is a library and isn't executed in an external process.

  === About SilverCity ===
  !SilverCity uses the lexer from [http://www.scintilla.org/ Scintilla]. Scintilla supports more languages than !SilverCity implements. If you want to add a language to !SilverCity supported by Scintilla, it's not very difficult. See [http://projects.edgewall.com/trac/wiki/SilverCityAddLanguage SilverCityAddLanguage] for some information how.


  == Syntax Coloring Support ==

  || || !SilverCity || Enscript ||
  || Ada      ||   || X ||
  || Asm      ||   || X ||
  || * ASP    || X || X ||
  || * C      || X || X ||
  || * C++    || X || X ||
  || * Java   ||   || X ||
  || Awk      ||   || X ||
  || CSS      || X ||   ||
  || Diff     ||   || X ||
  || Eiffel   ||   || X ||
  || Elisp    ||   || X ||
  || Fortran  ||   || X ||
  || Haskell  ||   || X ||
  || HTML     || X || X ||
  || IDL      ||   || X ||
  || Javascript || X || X ||

  || m4       ||   || X ||
  || Makefile ||   || X ||
  || Matlab   ||   || X ||
  || Objective-C|| || X ||
  || Pascal   ||   || X ||
  || * Perl   || X || X ||
  || * PHP    || X || X ||
  || PSP      || X ||   ||
  || Pyrex    ||   || X ||
  || * Python || X || X ||
  || * Ruby   || X || X (1) ||
  || Scheme   ||   || X ||
  || Shell    ||   || X ||
  || SQL      || X || X ||
  || Troff    ||   || X ||
  || TCL      ||   || X ||
  || Tex      ||   || X ||
  || Verilog  ||   || X ||
  || VHDL     ||   || X ||
  || Visual Basic |||| X ||
  || VRML     ||   || X ||
  || XML      || X || X ||

  ''(*) Supported as inline code blocks in [wiki:WikiFormatting Wiki text] using WikiProcessors.''

  ''(1) Ruby highlighting is not included in the Enscript distribution.  Highlighting rules for Ruby can be obtained from: http://neugierig.org/software/ruby/

  == Extra Software ==
   * GNU Enscript -- http://people.ssh.fi/mtr/genscript/
   * !SilverCity -- http://silvercity.sf.net/

  ----
  See also: WikiProcessors, WikiFormatting, TracWiki, TracBrowser


name: TracTimeline
author: trac
ipnr: 127.0.0.1
text:
  = The Trac Timeline =
  [[TracGuideToc]]

  The timeline provides a historic view of the project in a single report.

  It lists all Trac events that have occured in chronological order, a
  brief description of each event and if applicable, the person responsible for
  the change.

  The timeline lists these kinds of events:
   * '''Wiki page events''' -- Creation and changes
   * '''Ticket events''' -- Creation and resolution/closing (and optionally other changes)
   * '''Source code changes ''' -- Repository check-ins
   * '''Milestone ''' -- Milestone completed

  Each event entry provides a hyperlink to the specific event in question, as well as
  a brief excerpt of the actual comment or text, if available.

  == RSS Support ==

  The Timeline module supports subscription using RSS 2.0 syndication. To subscribe to project events, click orange '''XML''' icon at the bottom of the page. See TracRss for more information on RSS support in Trac.

  ----
  See also: TracGuide, TracWiki, WikiFormatting, TracRss, TracNotification


name: WikiRestructuredTextLinks
author: trac
ipnr: 127.0.0.1
text:
  = TracLinks in reStructuredText =

  This document is for testing the ``..trac::`` directive. The page is written like

  {{{
  {{{
  #!rst 

  Examples
  ...
  ...

  }}}
  }}}


  This is a list of example uses of the ''trac'' directive, providing use of TracLinks in WikiRestructuredText.

  {{{
  #!rst

  Examples
  --------

  trac role
  =========
  Syntax is \`link\`\:trac: or :trac:\`link\`, and could be put anywhere in the text. 'link' has the same format as explain for the ``.. trac::`` directive below.

  ``In the middle of my text `WikiFormatting`:trac: see!!!!`` 
     In the middle of my text `WikiFormatting`:trac: see!!!!

  or

  ``In the middle of my text :trac:`WikiFormatting` see!!!!`` 
     In the middle of my text :trac:`WikiFormatting` see!!!!


  wiki
  ====
  ``.. trac:: WikiFormatting``
  	.. trac:: WikiFormatting

  ``.. trac:: wiki:WikiFormatting``
         .. trac:: wiki:WikiFormatting

  ``.. trac:: wiki:WikiFormatting WikiFormatting``
  	.. trac:: wiki:WikiFormatting WikiFormatting

  ``.. trac:: wiki:WikiFormatting LinkText``
  	.. trac:: wiki:WikiFormatting LinkText

  tickets
  =======

  ``.. trac:: #1``
  	.. trac:: #1
  ``.. trac:: #1 ticket one``
  	.. trac:: #1 ticket one
  ``.. trac:: ticket:1``
  	.. trac:: ticket:1
  ``.. trac:: ticket:1 ticket one``
  	.. trac:: ticket:1 ticket one

  reports
  =======

  ``.. trac:: {1}``
  	.. trac:: {1}
  ``.. trac:: {1} report one``
          .. trac:: {1} report one
  ``.. trac:: report:1``
  	.. trac:: report:1
  ``.. trac:: report:1 report one``
  	.. trac:: report:1 report one

  changesets
  ==========

  ``.. trac:: [42]``
  	.. trac:: [42]
  ``.. trac:: [42] changeset 42``
  	.. trac:: [42] changeset 42
  ``.. trac:: changeset:42``
  	.. trac:: changeset:42
  ``.. trac:: changeset:42 changeset 42``
  	.. trac:: changeset:42 changeset 42
  ``.. trac:: foo``
  	.. trac:: foo

  files
  =====

  ``.. trac:: browser:/trunk/trac``
  	.. trac:: browser:/trunk/trac

  The leading ``/`` can be omitted...

  ``.. trac:: repos:trunk/trac trunk/trac``
  	.. trac:: repos:trunk/trac trunk/trac
  ``.. trac:: source:trunk/trac Trac source code``
  	.. trac:: source:trunk/trac Trac source code

  ``.. trac:: browser:trunk/README``
  	.. trac:: browser:trunk/README
  ``.. trac:: repos:trunk/README trunk/README``
  	.. trac:: repos:trunk/README trunk/README
  ``.. trac:: source:trunk/README README in trunk``
  	.. trac:: source:trunk/README README in trunk

  Note that if ``hoo`` is a file, the link targets its revision log. In order to see the file's content, you need to specify the revision explicitely, like here:

  ``.. trac:: browser:/trunk/README#latest latest of trunk/README``
  	.. trac:: browser:/trunk/README#latest latest of trunk/README
  ``.. trac:: repos:trunk/README#42 trunk/README in rev 42``
  	.. trac:: repos:trunk/README#42 trunk/README in rev 42
  }}}

  ----
  See also: WikiRestructuredTextLinks, TracLinks


name: TracBrowser
author: trac
ipnr: 127.0.0.1
text:
  = 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


name: TracCgi
author: trac
ipnr: 127.0.0.1
text:
  = 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


name: TracIni
author: trac
ipnr: 127.0.0.1
text:
  = 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] ==
  || `database`        || [wiki:TracEnvironment#DatabaseConnectionStrings Database connection string] for this project ||
  || `default_charset` || Charset used in text files in the subversion repository (default is `iso-8859-15`) ||
  || `default_handler` || Name of the component that handles requests to the base URL (default is `WikiHandler`) (''since 0.9'') ||
  || `repository_dir`  || Path to local Subversion repository ||
  || `authz_file`      || Path to Subversion [http://svnbook.red-bean.com/en/1.1/ch06s04.html#svn-ch-6-sect-4.4.2 authorization (authz) file]. ||
  || `authz_module_name` || The module prefix used in the `authz_file` (See FineGrainedPermissions)||
  || `check_auth_ip` || Whether the IP address of the user should be checked for authentication (true, false) (''since 0.9'') ||
  || `ignore_auth_case` || Whether case should be ignored for login names (true, false) (''since 0.9'') ||
  || `templates_dir`   || Path to the !ClearSilver templates ||

  == [project] ==
  || `name`   || Project name ||
  || `descr`  || Short project description ||
  || `url`    || URL to the main project website ||
  || `icon`   || URL to icon file to use as shortcut icon (favicon) ||
  || `footer` || Page footer text (right-aligned) ||

  == [header_logo] ==
  || `src`    || URL to image to use as header logo ||
  || `link`   || Destination URL to link to from header logo ||
  || `alt`    || ''alt'' text for header logo ||
  || `width`  || Header logo width in pixels ||
  || `height` || Header logo height in pixels ||
  See also: TracInterfaceCustomization.

  == [logging] ==
  || `log_type`  || Logging facility to use. (none, file, stderr, syslog, winlog) ||
  || `log_file`  || If ''log_type'' is ''file'', this should be a path to the log-file ||
  || `log_level` || Level of verbosity in log (CRITICAL, ERROR, WARN, INFO, DEBUG) ||
  See also: TracLogging

  == [attachment] ==
  || `max_size` || Maximum allowed file size for ticket and wiki attachments ||

  == [notification] ==
  || `smtp_enabled`   || Enable SMTP (email) notification (true, false) ||
  || `smtp_server`    || SMTP server to use for email notifications ||
  || `smtp_user`      || Username for SMTP server (''since 0.9'') ||
  || `smtp_password`  || Password for SMTP server (''since 0.9'') ||
  || `smtp_from`      || Sender address to use in notification emails ||
  || `smtp_replyto`   || Reply-To address to use in notification emails ||
  || `smtp_always_cc` || Email address(es) to always send notifications to ||
  || `always_notify_reporter` || Always send notifications to any address in the ''reporter'' field ||
  || `always_notify_owner` || Always send notifications to the ticket owner (''since 0.9'') ||
  See also: TracNotification

  == [mimeviewer] ==
  || `enscript_path` || Path to the Enscript program ||
  || `php_path` || Path to the PHP program ||
  || `max_preview_size` || Maximum file size for HTML preview (''since 0.9'') ||
  || `tab_width` || Displayed tab width in file preview (''since 0.9'') ||

  == [ticket] ==
  || `default_version`   || Default version for newly created tickets ||
  || `default_severity`  || Default severity for newly created tickets ||
  || `default_priority`  || Default priority for newly created tickets ||
  || `default_milestone` || Default milestone for newly created tickets ||
  || `default_component` || Default component for newly created tickets ||
  || `restrict_owner`    || Make the owner field of tickets use a drop-down menu (''since 0.9'') ||

  == [ticket-custom] ==
  Creates [wiki:TracTicketsCustomFields user-defined ticket fields].

  == [timeline] ==
  || `default_daysback` || Default "depth" of the Timeline, in days (''since 0.9'') ||
  || `changeset_show_files` || Number of files to show (-1 for unlimited, 0 to disable) ||
  || `ticket_show_details` || Enable the display of all ticket changes in the timeline ||

  == [browser] ==
  || `hide_properties` || List of subversion properties to hide from the repository browser (''since 0.9'') ||

  == [wiki] ==
  || `ignore_missing_pages` || enable/disable highlighting CamelCase links to missing pages (''since 0.9'') ||

  == [components] ==
  (''since 0.9'')

  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 [wiki:TracReports 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.

  See the ''Plugins'' page on ''About Trac'' to get the list of active components (requires `CONFIG_VIEW` [wiki:TracPermissions permissions].)

  See also: TracPlugins

    ''Note that prior to Trac r2335 (that applies to 0.9b1 and 0.9b2), you would use a `[disabled_components]` section instead. See a [http://projects.edgewall.com/trac/wiki/TracIni?version=42 previous version] of this page for the details.''

  ----
  See also: TracGuide, TracAdmin, TracEnvironment


name: TracRss
author: trac
ipnr: 127.0.0.1
text:
  = Using RSS with Trac =
  [[TracGuideToc]]

  Several of the Trac modules support content syndication using the RSS (Really Simple Syndication) XML format.
  Using the RSS subscription feature in Trac, you can easily monitor progress of the project, a set of issues or even changes to a single file .

  Trac supports RSS feeds in:

   * TracTimeline --  Use the RSS feed to '''subscribe to project events'''.[[br]]Monitor overall project progress in your favorite RSS reader.
   * TracReports and TracQuery -- Allows syndication of report and ticket query results.[[br]]Be notified about important and relevant issue tickets.
   * TracBrowser -- Syndication of file changes.[[br]]Stay up to date with changes to a specific file or directory.

  == How to access RSS data ==
  Anywhere in Trac where RSS is available, you should find a small orange '''XML''' icon, typically placed at the bottom of the page. Clicking the icon will access the RSS feed for that specific resource.

  '''Note:''' Different modules provide different data in their RSS feeds. Usually, the syndicated information corresponds to the current view. For example, if you click the RSS link on a report page, the feed will be based on that report. It might be explained by thinking of the RSS feeds as an ''alternate view of the data currently displayed''.

  == Links ==
   * http://blogs.law.harvard.edu/tech/rss -- RSS 2.0 Specification
   * http://www.mozilla.org/products/firefox/ -- Mozilla Firefox supports [http://www.mozilla.org/products/firefox/live-bookmarks.html live bookmarks] using RSS
   * http://sage.mozdev.org -- Sage RSS and Atom feed aggregator for Mozilla Firefox
   * http://www.rssreader.com/ -- Free and powerful RSS Reader for Windows
   * http://liferea.sourceforge.net/ -- Open source GTK2 RSS Reader for Linux
   * http://akregator.sourceforge.net/ -- Open source KDE RSS Reader (will be part of KDE-PIM 3.4)
   * http://www.sharpreader.net/ -- A free RSS Reader written in .NET for Windows
  ----
  See also: TracGuide, TracTimeline, TracReports, TracBrowser


name: WikiFormatting
author: trac
ipnr: 127.0.0.1
text:
  = WikiFormatting =
  [[TracGuideToc]]

  Wiki markup is a core feature in Trac, tightly integrating all the other parts of Trac into a flexible and powerful whole.

  Trac has a built in small and powerful wiki rendering engine. This wiki engine implements an ever growing subset of the commands from other popular Wikis,
  especially [http://moinmoin.wikiwikiweb.de/ MoinMoin]. 


  This page demonstrates the formatting syntax available anywhere WikiFormatting is allowed.


  == Font Styles ==

  The Trac wiki supports the following font styles:
  {{{
   * '''bold'''
   * ''italic''
   * '''''bold italic'''''
   * __underline__
   * {{{monospace}}} or `monospace`
   * ~~strike-through~~
   * ^superscript^ 
   * ,,subscript,,
  }}}

  Display:
   * '''bold'''
   * ''italic''
   * '''''bold italic'''''
   * __underline__
   * {{{monospace}}} or `monospace`
   * ~~strike-through~~
   * ^superscript^ 
   * ,,subscript,,

  Note that the `{{{...}}}` and {{{`...`}}} commands not only select a monospace font, but also treat their content as verbatim text, meaning that no further wiki processing is done on this text.

  == Headings ==

  You can create heading by starting a line with one up to five ''equal'' characters ("=")
  followed by a single space and the headline text. The line should end with a space 
  followed by the same number of ''='' characters.

  Example:
  {{{
  = Heading =
  == Subheading ==
  === About ''this'' ===
  }}}

  Display:
  = Heading =
  == Subheading ==
  === About ''this'' ===


  == Paragraphs ==

  A new text paragraph is created whenever two blocks of text are separated by one or more empty lines.

  A forced line break can also be inserted, using:
  {{{
  Line 1[[BR]]Line 2
  }}}
  Display:

  Line 1[[BR]]Line 2


  == Lists ==

  The wiki supports both ordered/numbered and unordered lists.

  Example:
  {{{
   * Item 1
     * Item 1.1
   * Item 2

   1. Item 1
     1. Item 1.1
   1. Item 2
  }}}

  Display:
   * Item 1
     * Item 1.1
   * Item 2

   1. Item 1
     1. Item 1.1
   1. Item 2

  Note that there must be one or more spaces preceding the list item markers, otherwise the list will be treated as a normal paragraph.


  == Definition Lists ==

  The wiki also supports definition lists.

  Example:
  {{{
   llama::
     some kind of mammal, with hair
   ppython::
     some kind of reptile, without hair
     (can you spot the typo?)
  }}}

  Display:
   llama::
     some kind of mammal, with hair
   ppython::
     some kind of reptile, without hair
     (can you spot the typo?)

  Note that you need a space in front of the defined term.


  == Preformatted Text ==

  Block containing preformatted text are suitable for source code snippets, notes and examples. Use three ''curly braces'' wrapped around the text to define a block quote. The curly braces need to be on a separate line.
    
  Example:
  {{{
   {{{
    def HelloWorld():
        print "Hello World"
   }}}
  }}}

  Display:
  {{{
   def HelloWorld():
       print "Hello World"
  }}}


  == Blockquotes ==

  In order to mark a paragraph as blockquote, indent that paragraph with two spaces.

  Example:
  {{{
    This text is a quote from someone else.
  }}}

  Display:
    This text is a quote from someone else.

  == Tables ==

  Simple tables can be created like this:
  {{{
  ||Cell 1||Cell 2||Cell 3||
  ||Cell 4||Cell 5||Cell 6||
  }}}

  Display:
  ||Cell 1||Cell 2||Cell 3||
  ||Cell 4||Cell 5||Cell 6||

  Note that more complex tables can be created using
  [wiki:WikiRestructuredText#BiggerReSTExample reStructuredText].


  == Links ==

  Hyperlinks are automatically created for WikiPageNames and URLs. !WikiPageLinks can be disabled by prepending an exclamation mark "!" character, such as {{{!WikiPageLink}}}.

  Example:
  {{{
   TitleIndex, http://www.edgewall.com/, !NotAlink
  }}}

  Display:
   TitleIndex, http://www.edgewall.com/, !NotAlink

  Links can be given a more descriptive title by writing the link followed by a space and a title and all this inside square brackets.  If the descriptive title is omitted, then the explicit prefix is disguarded, unless the link is an external link. This can be useful for wiki pages not adhering to the WikiPageNames convention.

  Example:
  {{{
   * [http://www.edgewall.com/ Edgewall Software]
   * [wiki:TitleIndex Title Index]
   * [wiki:ISO9000]
  }}}

  Display:
   * [http://www.edgewall.com/ Edgewall Software]
   * [wiki:TitleIndex Title Index]
   * [wiki:ISO9000]


  === Trac Links ===

  Wiki pages can link directly to other parts of the Trac system. Pages can refer to tickets, reports, changesets, milestones, source files and other Wiki pages using the following notations:
  {{{
   * Tickets: #1 or ticket:1
   * Reports: {1} or report:1
   * Changesets: r1, [1] or changeset:1
   * Revision Logs: r1:3, [1:3] or log:branches/0.8-stable#1:3
   * Wiki pages: CamelCase or wiki:CamelCase
   * Milestones: milestone:1.0 or milestone:"End-of-days Release"
   * Files: source:trunk/COPYING
   * Attachments: attachment:"file name.doc"
   * A specific file revision: source:/trunk/COPYING#200
   * A filename with embedded space: source:"/trunk/README FIRST"
  }}}

  Display:
   * Tickets: #1 or ticket:1
   * Reports: {1} or report:1
   * Changesets: r1, [1] or changeset:1
   * Revision Logs: r1:3, [1:3] or log:branches/0.8-stable#1:3
   * Wiki pages: CamelCase or wiki:CamelCase
   * Milestones: milestone:1.0 or milestone:"End-of-days Release"
   * Files: source:trunk/COPYING
   * Attachments: attachment:"file name.doc"
   * A specific file revision: source:/trunk/COPYING#200
   * A filename with embedded space: source:"/trunk/README FIRST"

  See TracLinks for more in-depth information.


  == Escaping Links and WikiPageNames ==

  You may avoid making hyperlinks out of TracLinks by preceding an expression with a single "!" (exclamation mark).

  Example:
  {{{
   !NoHyperLink
   !#42 is not a link
  }}}

  Display:
   !NoHyperLink
   !#42 is not a link


  == Images ==

  Urls ending with `.png`, `.gif` or `.jpg` are automatically interpreted as image links, and converted to `<img>` tags.

  Example:
  {{{
  http://www.edgewall.com/gfx/trac_example_image.png
  }}}

  Display:

  http://www.edgewall.com/gfx/trac_example_image.png

  However, this doesn't give much control over the display mode. This way of inserting images is deprecated in favor of the more powerful `Image` macro (see WikiMacros).


  == Macros ==

  Macros are ''custom functions'' to insert dynamic content in a page.

  Example:
  {{{
   [[Timestamp]]
  }}}

  Display:
   [[Timestamp]]

  See WikiMacros for more information, and a list of installed macros.


  == Processors ==

  Trac supports alternative markup formats using WikiProcessors. For example, processors are used to write pages in 
  [wiki:WikiRestructuredText reStructuredText] or [wiki:WikiHtml HTML]. 

  Example 1:
  {{{
  #!html
  <pre class="wiki">{{{
  #!html
  &lt;h1 style="text-align: right; color: blue"&gt;HTML Test&lt;/h1&gt;
  }}}</pre>
  }}}

  Display:
  {{{
  #!html
  <h1 style="text-align: right; color: blue">HTML Test</h1>
  }}}

  Example:
  {{{
  #!html
  <pre class="wiki">{{{
  #!python
  class Test:
      def __init__(self):
          print "Hello World"
  if __name__ == '__main__':
     Test()
  }}}</pre>
  }}}

  Display:
  {{{
  #!python
  class Test:
      def __init__(self):
          print "Hello World"
  if __name__ == '__main__':
     Test()
  }}}

  Perl:
  {{{
  #!perl
  my ($test) = 0;
  if ($test > 0) {
  echo "hello";
  }
  }}}

  See WikiProcessors for more information.


  == Miscellaneous ==

  Four or more dashes will be replaced by a horizontal line (<HR>)

  Example:
  {{{
   ----
  }}}

  Display:
  ----


  ----
  See also: TracLinks, TracGuide, WikiHtml, WikiMacros, WikiProcessors, TracSyntaxColoring.


name: TracSearch
author: trac
ipnr: 127.0.0.1
text:
  = Using Search =

  Trac has a built-in search engine to allow finding occurrences of keywords and substrings in wiki pages, tickets and changeset descriptions.

  Using the Trac search facility is straightforward and its interface should be familiar to most www users.

  Apart from the [search: Search module], you will also find a small search field above the navigation bar at all time. It provides convenient access to the search module from all pages.

  == Quickjumps ==
  For intermediate and advanced use, Trac has a useful way to quickly navigate to a given resource, named '''quickjumps'''.

  If you enter a [wiki:TracLinks TracLink] in the search field above the navigation bar, Trac will recognize this and assume you know where you're going. 

  For example:

   * ![42] -- Opens change set 42
   * !#42 -- Opens ticket number 42
   * !{1} -- Opens report 1

  '''Note:''' ''This is a particularly useful feature to quickly navigate to a specific issue ticket or changeset.''

  === Advanced: Disabling Quickjumps ===
  To disable the quickjump feature for a search keyword - for example when searching for occurences of the literal word !TracGuide - begin the query with an exclamation mark (!).

  ----
  See also: TracGuide, TracLinks, TracQuery


name: WikiProcessors
author: trac
ipnr: 127.0.0.1
text:
  = Wiki Processors =
  Processors are WikiMacros designed to provide alternative markup formats for the Trac Wiki engine. Processors can be thought of as ''macro functions to process user-edited text''. 

  The wiki engine uses processors to allow using [wiki:WikiRestructuredText Restructured Text] and [wiki:WikiHtml raw HTML] in any wiki text throughout Trac.

  == Using Processors ==
  To use a processor on a block of text, use a wiki blockquote, selecting a processor by name using ''shebang notation'' (#!), familiar to most UNIX users from scripts.

  '''Example 1''' (''inserting raw HTML in a wiki text''):

  {{{
  #!html
  <pre class="wiki">{{{
  #!html
  &lt;h1 style="color: orange"&gt;This is raw HTML&lt;/h1&gt;
  }}}</pre>
  }}}

  '''Results in:'''
  {{{
  #!html
  <h1 style="color: orange">This is raw HTML</h1>
  }}}

  ----

  '''Example 2''' (''inserting Restructured Text in wiki text''):

  {{{
  #!html
  <pre class="wiki">{{{
  #!rst
  A header
  --------
  This is some **text** with a footnote [*]_.

  .. [*] This is the footnote.
  }}}</pre>
  }}}

  '''Results in:'''
  {{{
  #!rst
  A header
  --------
  This is some **text** with a footnote [*]_.

  .. [*] This is the footnote.
  }}}
  ----
  '''Example 3''' (''inserting a block of C source code in wiki text''):

  {{{
  #!html
  <pre class="wiki">{{{
  #!c
  int main(int argc, char *argv[])
  {
    printf("Hello World\n");
    return 0;
  }
  }}}</pre>
  }}}

  '''Results in:'''
  {{{
  #!c
  int main(int argc, char *argv[])
  {
    printf("Hello World\n");
    return 0;
  }
  }}}

  ----

  == Available Processors ==
  The following processors are included in the Trac distribution:
   * '''html''' -- Insert custom HTML in a wiki page. See WikiHtml.
   * '''rst''' -- Trac support for Restructured Text. See WikiRestructuredText.
   * '''textile''' -- Supported if  [http://dealmeida.net/projects/textile/ Textile] is installed.

  === Code Highlighting Support ===
  Trac includes processors to provide inline [wiki:TracSyntaxColoring syntax highlighting] for the following languages:
   * '''c''' -- C
   * '''cpp''' -- C++
   * '''python''' -- Python
   * '''perl''' -- Perl
   * '''ruby''' -- Ruby
   * '''php''' -- PHP
   * '''asp''' --- ASP
   * '''sql''' -- SQL
   * '''xml''' -- XML
  '''Note:''' ''Trac relies on external software packages for syntax coloring. See TracSyntaxColoring for more info.''

  By using the MIME type as processor, it is possible to syntax-highlight the same languages that are supported when browsing source code. For example, you can write:
  {{{
  {{{
  #!text/html
  <h1>text</h1>
  }}}
  }}}

  The result will be syntax highlighted HTML code. The same is valid for all other mime types supported.


  For more processor macros developed and/or contributed by users, visit: 
   * [http://projects.edgewall.com/trac/wiki/ProcessorBazaar ProcessorBazaar]
   * [http://projects.edgewall.com/trac/wiki/MacroBazaar MacroBazaar]


  == Advanced Topics: Developing Processor Macros ==
  Developing processors is no different than WikiMacros. In fact they work the same way, only the usage syntax differs. See WikiMacros for more information.

  '''Example:''' (''Restructured Text Processor''):
  {{{
  from docutils.core import publish_string

  def execute(hdf, text, env):
      html = publish_string(text, writer_name = 'html')
      return html[html.find('<body>')+6:html.find('</body>')].strip()
  }}}

  ----
  See also: WikiMacros, WikiHtml, WikiRestructuredText, TracSyntaxColoring, WikiFormatting, TracGuide


name: WikiStart
author: anonymous
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =


  = Welcome to Trac 0.9.5 =

  Trac is a '''minimalistic''' approach to '''web-based''' management of
  '''software projects'''. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress.

  All aspects of Trac have been designed with the single goal to 
  '''help developers write great software''' while '''staying out of the way'''
  and imposing as little as possible on a team's established process and
  culture.

  As all Wiki pages, this page is editable, this means that you can
  modify the contents of this page simply by using your
  web-browser. Simply click on the "Edit this page" link at the bottom
  of the page. WikiFormatting will give you a detailed description of
  available Wiki formatting commands.

  "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created
  a new Trac environment, containing a default set of wiki pages and some sample
  data. This newly created environment also contains 
  [wiki:TracGuide documentation] to help you get started with your project.

  You can use [wiki:TracAdmin trac-admin] to configure
  [http://trac.edgewall.com/ Trac] to better fit your project, especially in
  regard to ''components'', ''versions'' and ''milestones''. 


  TracGuide is a good place to start.

  Enjoy! [[BR]]
  ''The Trac Team''

  == Starting Points ==

   * TracGuide --  Built-in Documentation
   * [http://projects.edgewall.com/trac/ The Trac project] -- Trac Open Source Project
   * [http://projects.edgewall.com/trac/wiki/TracFaq Trac FAQ] -- Frequently Asked Questions
   * TracSupport --  Trac Support

  For a complete list of local wiki pages, see TitleIndex.

  Trac is brought to you by [http://www.edgewall.com/ Edgewall Software],
  providing professional Linux and software development services to clients
  worldwide. Visit http://www.edgewall.com/ for more information.


name: WikiStart
author: anonymous
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  {{{
  = Welcome to Trac 0.9.5 =

  Trac is a '''minimalistic''' approach to '''web-based''' management of
  '''software projects'''. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress.

  All aspects of Trac have been designed with the single goal to 
  '''help developers write great software''' while '''staying out of the way'''
  and imposing as little as possible on a team's established process and
  culture.

  As all Wiki pages, this page is editable, this means that you can
  modify the contents of this page simply by using your
  web-browser. Simply click on the "Edit this page" link at the bottom
  of the page. WikiFormatting will give you a detailed description of
  available Wiki formatting commands.

  "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created
  a new Trac environment, containing a default set of wiki pages and some sample
  data. This newly created environment also contains 
  [wiki:TracGuide documentation] to help you get started with your project.

  You can use [wiki:TracAdmin trac-admin] to configure
  [http://trac.edgewall.com/ Trac] to better fit your project, especially in
  regard to ''components'', ''versions'' and ''milestones''. 


  TracGuide is a good place to start.

  Enjoy! [[BR]]
  ''The Trac Team''

  == Starting Points ==

   * TracGuide --  Built-in Documentation
   * [http://projects.edgewall.com/trac/ The Trac project] -- Trac Open Source Project
   * [http://projects.edgewall.com/trac/wiki/TracFaq Trac FAQ] -- Frequently Asked Questions
   * TracSupport --  Trac Support

  For a complete list of local wiki pages, see TitleIndex.

  Trac is brought to you by [http://www.edgewall.com/ Edgewall Software],
  providing professional Linux and software development services to clients
  worldwide. Visit http://www.edgewall.com/ for more information.
  }}}


name: WikiStart
author: anonymous
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  This will soon be more updated with various news and things I do over here.
  All the stuff for now is a bit experimental as I play with it.
  But soon when I realise how to do it well I will finish it and try to do a nice organised 
  site to have all the stuff usefull.

  = Welcome to Trac 0.9.5 =

  Trac is a '''minimalistic''' approach to '''web-based''' management of
  '''software projects'''. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress.

  All aspects of Trac have been designed with the single goal to 
  '''help developers write great software''' while '''staying out of the way'''
  and imposing as little as possible on a team's established process and
  culture.

  As all Wiki pages, this page is editable, this means that you can
  modify the contents of this page simply by using your
  web-browser. Simply click on the "Edit this page" link at the bottom
  of the page. WikiFormatting will give you a detailed description of
  available Wiki formatting commands.

  "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created
  a new Trac environment, containing a default set of wiki pages and some sample
  data. This newly created environment also contains 
  [wiki:TracGuide documentation] to help you get started with your project.

  You can use [wiki:TracAdmin trac-admin] to configure
  [http://trac.edgewall.com/ Trac] to better fit your project, especially in
  regard to ''components'', ''versions'' and ''milestones''. 


  TracGuide is a good place to start.

  Enjoy! [[BR]]
  ''The Trac Team''

  == Starting Points ==

   * TracGuide --  Built-in Documentation
   * [http://projects.edgewall.com/trac/ The Trac project] -- Trac Open Source Project
   * [http://projects.edgewall.com/trac/wiki/TracFaq Trac FAQ] -- Frequently Asked Questions
   * TracSupport --  Trac Support

  For a complete list of local wiki pages, see TitleIndex.

  Trac is brought to you by [http://www.edgewall.com/ Edgewall Software],
  providing professional Linux and software development services to clients
  worldwide. Visit http://www.edgewall.com/ for more information.


name: WikiStart
author: anonymous
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  This will soon be more updated with various news and things I do over here.
  All the stuff for now is a bit experimental as I play with it.
  But soon when I realise how to do it well I will finish it and try to do a nice organised 
  site to have all the stuff usefull.

  So for now you can browse the dropline-build-system sources here[http://linux.redos.si/trac/browser]

  Enjoy
  Saxa


name: WikiStart
author: anonymous
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  This will soon be more updated with various news and things I do over here.
  All the stuff for now is a bit experimental as I play with it.
  But soon when I realise how to do it well I will finish it and try to do a nice organised 
  site to have all the stuff usefull.

  So for now you can browse the dropline-build-system sources here [http://linux.redos.si/trac/browser]

  You can use the Tickets service available from [http://linux.redos.si/trac/report] and 
  from here [http://linux.redos.si/trac/newticket] . 

  Enjoy
  Saxa


name: WikiStart
author: anonymous
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  This will soon be more updated with various news and things I do over here.
  All the stuff for now is a bit experimental as I play with it.
  But soon when I realise how to do it well I will finish it and try to do a nice organised 
  site to have all the stuff usefull.

  So for now you can browse the dropline-build-system sources here [http://linux.redos.si/trac/browser]

  I will use the following directories and structure on the svn repository.

  branches/ - This will be used for the scripts I upgrade to the current release

  tags/ - Here will be the home of the last released scripts (all last scripts for release 2.14.2)

  trunk/ - Here you will find all commits of scripts and patches wich will change more frequently.


  You can use the Tickets service available from [http://linux.redos.si/trac/report] and 
  from here [http://linux.redos.si/trac/newticket] . 

  Enjoy
  Saxa


name: WikiStart
author: anonymous
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  This will soon be more updated with various news and things I do over here.
  All the stuff for now is a bit experimental as I play with it.
  But soon when I realise how to do it well I will finish it and try to do a nice organised 
  site to have all the stuff usefull.

  So for now you can browse the dropline-build-system sources here [http://linux.redos.si/trac/browser]

  I will use the following directories and structure on the svn repository.

  branches/ - This will be used for the scripts I upgrade to the current release

  tags/ - Here will be the home of the last released scripts (all last scripts for release 2.14.2)

  trunk/ - Here you will find all commits of scripts and patches wich will change more frequently.


  You can use the Tickets service available from [http://linux.redos.si/trac/report] and 
  from here [http://linux.redos.si/trac/newticket] . 

  Enjoy
  Saxa

  -------------------------------------------------------------
  OpenOffice.org with DroplineGNOME and Slackware

  This page will have soon some info about what I did and needed to do to make it work ;) News section Sunday 27-11-2005:

  We have a new OpenOffice.org package from Trovao !!!

  It is the v2.0.0 build and you can get it from here:

  http://www.droplinegnome.org/home/trovao/ooo/

  Many thanks trovao :)

  The screenshots are here: http://www.droplinegnome.org/home/saxa/ooo/screenshots/


  Please test it and report all the problems to my e-mail: casaxa@gmail.com or to the irc channel irc.freenode.net /join #ooo-slackware

  Ok the build scripts and everything else will be located here http://www.droplinegnome.org/home/saxa/ooo/

  If interested in helping me join me at irc.freenode.net /join #ooo-slackware

  Also some important things I found out till now are: Needed thinks to build it are the following:

    1. Slackware + DLG 2.12.1
    2. Mozilla is needed get it from [http://www.droplinegnome.org/home/diffie/
    3. Java j2sdk1.4.1_07 I have to try with the j2sdk1.4.2_07 which is the last release
    4. Ant - http://ant.apache.org/bindownload.cgi
    5. Perl5 on Slackware needs to update some modules.
           * module name: Archive::Zip
           * module name: XML::Parser
           * You install them by the following commands:
           * as root do:  # perl -MCPAN -e shell 
           * If it is the first time you do it, answer the questions and you will get the cpan> prompt at the end.
           * When you are at cpan> type the following:
           * cpan> install module_name 
           * after the install you can exit the shell by typing exit
    6. Get the source code from http://www.openoffice.org or from http://ooo.ximian.com

  Patches for compile with ooo-build are here: http://www.droplinegnome.org/home/saxa/ooo/patches/

  Use the correct patches for the configure option --with-distro=DroplineGNOME

  DroplineGNOME-ooo-build-2.0.0.1.diff <--- If you use that patch the following configure options are NOT needed.

  For configuring the beast I have gave this options to configure:

  cd into config_office/ and issue the command:


  ./configure \
  --prefix=/opt/ooo-2.0 \
  --enable-libart \
  --enable-libsn \
  --disable-epm \
  --with-system-stdlibs \
  --with-system-zlib \
  --with-system-jpeg \
  --with-system-expat \
  --with-system-freetype \
  --with-system-libxml \
  --with-system-python \
  --with-system-mozilla \ 
  --with-system-db \ 
  --with-system-sane-header \
  --with-system-curl \
  --with-system-sndfile \
  --with-ant-home=/usr/share/ant \
  --with-lang=ALL \
  --with-dict=ALL \
  --with-x \

  That is it for now. I will update the page as soon as I have some more time and more results.

  --SasaOstrouska 01:02, 27 November 2005 (CET) 


name: OpenOffice.org
author: anonymous
ipnr: 217.223.95.245
text:
  This page will have soon some info about what I did and needed to do to make it work ;) News section Sunday 27-11-2005:

  We have a new OpenOffice.org package from Trovao !!!

  It is the v2.0.0 build and you can get it from here:

  http://www.droplinegnome.org/home/trovao/ooo/

  Many thanks trovao :)

  The screenshots are here: http://www.droplinegnome.org/home/saxa/ooo/screenshots/


  Please test it and report all the problems to my e-mail: casaxa@gmail.com or to the irc channel irc.freenode.net /join #ooo-slackware

  Ok the build scripts and everything else will be located here http://www.droplinegnome.org/home/saxa/ooo/

  If interested in helping me join me at irc.freenode.net /join #ooo-slackware

  Also some important things I found out till now are: Needed thinks to build it are the following:

    1. Slackware + DLG 2.12.1
    2. Mozilla is needed get it from [http://www.droplinegnome.org/home/diffie/
    3. Java j2sdk1.4.1_07 I have to try with the j2sdk1.4.2_07 which is the last release
    4. Ant - http://ant.apache.org/bindownload.cgi
    5. Perl5 on Slackware needs to update some modules.
           * module name: Archive::Zip
           * module name: XML::Parser
           * You install them by the following commands:
           * as root do:  # perl -MCPAN -e shell 
           * If it is the first time you do it, answer the questions and you will get the cpan> prompt at the end.
           * When you are at cpan> type the following:
           * cpan> install module_name 
           * after the install you can exit the shell by typing exit
    6. Get the source code from http://www.openoffice.org or from http://ooo.ximian.com

  Patches for compile with ooo-build are here: http://www.droplinegnome.org/home/saxa/ooo/patches/

  Use the correct patches for the configure option --with-distro=DroplineGNOME

  DroplineGNOME-ooo-build-2.0.0.1.diff <--- If you use that patch the following configure options are NOT needed.

  For configuring the beast I have gave this options to configure:

  cd into config_office/ and issue the command:


  ./configure \
  --prefix=/opt/ooo-2.0 \
  --enable-libart \
  --enable-libsn \
  --disable-epm \
  --with-system-stdlibs \
  --with-system-zlib \
  --with-system-jpeg \
  --with-system-expat \
  --with-system-freetype \
  --with-system-libxml \
  --with-system-python \
  --with-system-mozilla \ 
  --with-system-db \ 
  --with-system-sane-header \
  --with-system-curl \
  --with-system-sndfile \
  --with-ant-home=/usr/share/ant \
  --with-lang=ALL \
  --with-dict=ALL \
  --with-x \

  That is it for now. I will update the page as soon as I have some more time and more results.

  --SasaOstrouska 01:02, 27 November 2005 (CET)


name: WikiStart
author: anonymous
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  This will soon be more updated with various news and things I do over here.
  All the stuff for now is a bit experimental as I play with it.
  But soon when I realise how to do it well I will finish it and try to do a nice organised 
  site to have all the stuff usefull.

  So for now you can browse the dropline-build-system sources here [http://linux.redos.si/trac/browser]

  I will use the following directories and structure on the svn repository.

  branches/ - This will be used for the scripts I upgrade to the current release

  tags/ - Here will be the home of the last released scripts (all last scripts for release 2.14.2)

  trunk/ - Here you will find all commits of scripts and patches wich will change more frequently.


  You can use the Tickets service available from [http://linux.redos.si/trac/report] and 
  from here [http://linux.redos.si/trac/newticket] . 

  Enjoy
  Saxa


name: WikiStart
author: anonymous
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  This will soon be more updated with various news and things I do over here.
  All the stuff for now is a bit experimental as I play with it.
  But soon when I realise how to do it well I will finish it and try to do a nice organised 
  site to have all the stuff usefull.

  So for now you can browse the dropline-build-system sources here [http://linux.redos.si/trac/browser]

  I will use the following directories and structure on the svn repository.

  * branches/ - This will be used for the scripts I upgrade to the current release

  * tags/ - Here will be the home of the last released scripts (all last scripts for release 2.14.2)

  * trunk/ - Here you will find all commits of scripts and patches wich will change more frequently.

  You can use the Tickets service available from [http://linux.redos.si/trac/report] and 
  from here [http://linux.redos.si/trac/newticket] . 

  --
  If you are looking for OpenOffice.org build instructions for Slackware and DroplineGNOME please look [[wiki:OpenOffice.org here]]

  Enjoy
  Saxa


name: OpenOffice.org
author: anonymous
ipnr: 217.223.95.245
text:
  This page will have soon some info about what I did and needed to do to make it work ;) News section Sunday 27-11-2005:

  We have a new OpenOffice.org package from Trovao !!!

  It is the v2.0.0 build and you can get it from here:

  http://www.droplinegnome.org/home/trovao/ooo/

  Many thanks trovao :)

  The screenshots are here: http://www.droplinegnome.org/home/saxa/ooo/screenshots/


  Please test it and report all the problems to my e-mail: casaxa@gmail.com or to the irc channel irc.freenode.net /join #ooo-slackware

  Ok the build scripts and everything else will be located here http://www.droplinegnome.org/home/saxa/ooo/

  If interested in helping me join me at irc.freenode.net /join #ooo-slackware

  Also some important things I found out till now are: Needed thinks to build it are the following:

    1. Slackware + DLG 2.12.1
    2. Mozilla is needed get it from [http://www.droplinegnome.org/home/diffie/
    3. Java j2sdk1.4.1_07 I have to try with the j2sdk1.4.2_07 which is the last release
    4. Ant - http://ant.apache.org/bindownload.cgi
    5. Perl5 on Slackware needs to update some modules.
           * module name: Archive::Zip
           * module name: XML::Parser
           * You install them by the following commands:
           * as root do:  # perl -MCPAN -e shell 
           * If it is the first time you do it, answer the questions and you will get the cpan> prompt at the end.
           * When you are at cpan> type the following:
           * cpan> install module_name 
           * after the install you can exit the shell by typing exit
    6. Get the source code from http://www.openoffice.org or from http://ooo.ximian.com

  Patches for compile with ooo-build are here: http://www.droplinegnome.org/home/saxa/ooo/patches/

  Use the correct patches for the configure option --with-distro=DroplineGNOME

  DroplineGNOME-ooo-build-2.0.0.1.diff <--- If you use that patch the following configure options are NOT needed.

  For configuring the beast I have gave this options to configure:

  cd into config_office/ and issue the command:

  {{{
  ./configure \
  --prefix=/opt/ooo-2.0 \
  --enable-libart \
  --enable-libsn \
  --disable-epm \
  --with-system-stdlibs \
  --with-system-zlib \
  --with-system-jpeg \
  --with-system-expat \
  --with-system-freetype \
  --with-system-libxml \
  --with-system-python \
  --with-system-mozilla \ 
  --with-system-db \ 
  --with-system-sane-header \
  --with-system-curl \
  --with-system-sndfile \
  --with-ant-home=/usr/share/ant \
  --with-lang=ALL \
  --with-dict=ALL \
  --with-x \
  }}}
  That is it for now. I will update the page as soon as I have some more time and more results.

  --SasaOstrouska 01:02, 27 November 2005 (CET)


name: DroplineInstaller
author: anonymous
ipnr: 217.223.95.245
text:
  ==Dropline Installer==

  This should be an descriptionof how the Dropline Installer should work and what it should do.

  This page will have more details very soon :)
  Thanks for the initiative to Johnny Mast :)

  Rgds
  Saxa


  ----

  Ok lets begin from the beginning. So what the dropline installer should be. In the text I will use 
  DLGI abreviation for droplinegnome-installer.

  So DLGI is an app which runs on a Slackware system and helps you to install the GNOME desktop
  packaged by the DroplineGNOME team. 
  The DLGI should have the following functionalities:

  - Should run in a non X enviroment, this because we do not have always X installed on Slackware where we want to install DroplineGNOME.

  - Should run in a X graphical enviroment without GNOME installed. As slackware uses XFCE I beleave it can be written in GTK+.

  - Should run also in a GNOME enviroment.

  - Should check for updates of the new awailable packages we made available on sf.net and mirrors.

  - Should allow you to only download the the packages. 

  - Should allow you to install packages from a .iso we supply.

  - Should allow you to select a mirror from where to download the packages.

  ----
  Ok lets go to see how the installer should do all the tasks.

  === Non graphical enviroment: ===

  If we run the installer as a non root user it should warn you that you will not be able to install the packages untill you supply the root password, but it should allow you to download the packages of course storing them into users home dir and let you select the mirror. Same thing is for updating the system. If run as a non root user it should allow only to download the updates.

  Also it should check if we have all the required system components (kernel version, X enviroment, which libs, networking and so on). 

  We should have a sort of choosing option on which Slackware version we want to install the packages on. So if we choose Slackwares previous release it should automatically download the correct packages released for that Slackware release. 

  Example: Choose Slackware 10.2 -> installs DroplineGNOME 2.14.x 

  It should also allow you to install the various dot releases we had. 

  Example: Slackware 10.2 -> selects DroplineGNOME 2.14.0, 2.14.1, 2.14.2 or 2.14.3

  After we have seleceted the release of DroplineGNOME it should be able to supply us the list of the mirrors where the packages are available on. It can give us also an option to enter an URL of choice. When we selected the mirror
  It should check if it finds the correct DroplineFiles2.14 file where the packages are listed. If it does not find the file should wanr that without it it can install or cant continue and let us choose again.

  when we selected an mirror and it has all the data necessary it should ask if we want to download only the packages or if we want to install them also.

  After that the installer should look and download the DroplineFiles2.14 file and beguin downloading the packages
  from the selected mirror. 

  When downloading is finished it should check the downloaded packages integrity with the md5 files and if some package is broken it should redownload it, if everything is ok it should begin installing the packages according to the order listed in the DroplineFiles2.14 file.

  The DLGI should use the Slackwares pkgtools like installpkg, upgradepkg, removepkg.

  When it finishes to install it should ask the user if it wants to restart the sstem or only logout.

  The DLGI should also be able to change the inittab file in /etc to runlevel 4 so when we restart the machine after the sucessful installation we get the GDM page.

  Of course if the DLGI detects that the DroplineGNOME is already installed it should prompt the user what to do.
  The options can be Upgrade/Downgrade the system to a different version or Uninstall the DroplineGNOME Desktop.

  If the Uninstall option is choosen the DLGI should be able to restore the Slackware system according to the Slackware version installed.

  ----
  === Graphical mode: ===

  In the graphical mode the DLGI should act the same way as in the NON graphical mode except that it has a 
  frontend in GTK+.


  ----

  This is a raw description of how the installer should work.
  This information will be updated according to the necessarity during the coding of the installer.
  Written by Sasa Ostrouska 26-09-2006 , thats also my birthday :))
  ----

  = Drawings =
  ----

  = Stage 1: = 
  [[Image:Example.jpg]]


name: DroplineInstaller
author: anonymous
ipnr: 217.223.95.245
text:
  == Dropline Installer ==

  This should be an descriptionof how the Dropline Installer should work and what it should do.

  This page will have more details very soon :)
  Thanks for the initiative to Johnny Mast :)

  Rgds
  Saxa


  ----

  Ok lets begin from the beginning. So what the dropline installer should be. In the text I will use 
  DLGI abreviation for droplinegnome-installer.

  So DLGI is an app which runs on a Slackware system and helps you to install the GNOME desktop
  packaged by the DroplineGNOME team. 
  The DLGI should have the following functionalities:

  - Should run in a non X enviroment, this because we do not have always X installed on Slackware where we want to install DroplineGNOME.

  - Should run in a X graphical enviroment without GNOME installed. As slackware uses XFCE I beleave it can be written in GTK+.

  - Should run also in a GNOME enviroment.

  - Should check for updates of the new awailable packages we made available on sf.net and mirrors.

  - Should allow you to only download the the packages. 

  - Should allow you to install packages from a .iso we supply.

  - Should allow you to select a mirror from where to download the packages.

  ----
  Ok lets go to see how the installer should do all the tasks.

  === Non graphical enviroment: ===

  If we run the installer as a non root user it should warn you that you will not be able to install the packages untill you supply the root password, but it should allow you to download the packages of course storing them into users home dir and let you select the mirror. Same thing is for updating the system. If run as a non root user it should allow only to download the updates.

  Also it should check if we have all the required system components (kernel version, X enviroment, which libs, networking and so on). 

  We should have a sort of choosing option on which Slackware version we want to install the packages on. So if we choose Slackwares previous release it should automatically download the correct packages released for that Slackware release. 

  Example: Choose Slackware 10.2 -> installs DroplineGNOME 2.14.x 

  It should also allow you to install the various dot releases we had. 

  Example: Slackware 10.2 -> selects DroplineGNOME 2.14.0, 2.14.1, 2.14.2 or 2.14.3

  After we have seleceted the release of DroplineGNOME it should be able to supply us the list of the mirrors where the packages are available on. It can give us also an option to enter an URL of choice. When we selected the mirror
  It should check if it finds the correct DroplineFiles2.14 file where the packages are listed. If it does not find the file should wanr that without it it can install or cant continue and let us choose again.

  when we selected an mirror and it has all the data necessary it should ask if we want to download only the packages or if we want to install them also.

  After that the installer should look and download the DroplineFiles2.14 file and beguin downloading the packages
  from the selected mirror. 

  When downloading is finished it should check the downloaded packages integrity with the md5 files and if some package is broken it should redownload it, if everything is ok it should begin installing the packages according to the order listed in the DroplineFiles2.14 file.

  The DLGI should use the Slackwares pkgtools like installpkg, upgradepkg, removepkg.

  When it finishes to install it should ask the user if it wants to restart the sstem or only logout.

  The DLGI should also be able to change the inittab file in /etc to runlevel 4 so when we restart the machine after the sucessful installation we get the GDM page.

  Of course if the DLGI detects that the DroplineGNOME is already installed it should prompt the user what to do.
  The options can be Upgrade/Downgrade the system to a different version or Uninstall the DroplineGNOME Desktop.

  If the Uninstall option is choosen the DLGI should be able to restore the Slackware system according to the Slackware version installed.

  ----
  === Graphical mode: ===

  In the graphical mode the DLGI should act the same way as in the NON graphical mode except that it has a 
  frontend in GTK+.


  ----

  This is a raw description of how the installer should work.
  This information will be updated according to the necessarity during the coding of the installer.
  Written by Sasa Ostrouska 26-09-2006 , thats also my birthday :))
  ----

  = Drawings =
  ----

  = Stage 1: = 
  [[Image:Example.jpg]]


name: WikiStart
author: anonymous
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  This will soon be more updated with various news and things I do over here.
  All the stuff for now is a bit experimental as I play with it.
  But soon when I realise how to do it well I will finish it and try to do a nice organised 
  site to have all the stuff usefull.

  So for now you can browse the dropline-build-system sources here [http://linux.redos.si/trac/browser]

  I will use the following directories and structure on the svn repository.

  * branches/ - This will be used for the scripts I upgrade to the current release

  * tags/ - Here will be the home of the last released scripts (all last scripts for release 2.14.2)

  * trunk/ - Here you will find all commits of scripts and patches wich will change more frequently.

  You can use the Tickets service available from [http://linux.redos.si/trac/report] and 
  from here [http://linux.redos.si/trac/newticket] . 

  ----

  If you are looking for OpenOffice.org build instructions for Slackware and DroplineGNOME please look [[wiki:OpenOffice.org here]]

  For Dropline Installer please look [[wiki:DroplineInstaller here]]

  Enjoy
  Saxa


name: WikiStart
author: anonymous
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  This will soon be more updated with various news and things I do over here.
  All the stuff for now is a bit experimental as I play with it.
  But soon when I realise how to do it well I will finish it and try to do a nice organised 
  site to have all the stuff usefull.

  So for now you can browse the dropline-build-system sources here [http://linux.redos.si/trac/browser]

  I will use the following directories and structure on the svn repository.

  * branches/ - This will be used for the scripts I upgrade to the current release

  * tags/ - Here will be the home of the last released scripts (all last scripts for release 2.14.2)

  * trunk/ - Here you will find all commits of scripts and patches wich will change more frequently.

  You can use the Tickets service available from [http://linux.redos.si/trac/report] and 
  from here [http://linux.redos.si/trac/newticket] . 

  ----

  If you are looking for '''OpenOffice.org''' build instructions for Slackware and DroplineGNOME please look [[wiki:OpenOffice.org here]]

  For '''Dropline Installer''' please look [[wiki:DroplineInstaller here]]

  Enjoy
  Saxa


name: WikiStart
author: anonymous
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  This will soon be more updated with various news and things I do over here.
  All the stuff for now is a bit experimental as I play with it.
  But soon when I realise how to do it well I will finish it and try to do a nice organised 
  site to have all the stuff usefull.

  So for now you can browse the dropline-build-system sources here [http://linux.redos.si/trac/browser]

  I will use the following directories and structure on the svn repository.

  * branches/ - This will be used for the scripts I upgrade to the current release

  * tags/ - Here will be the home of the last released scripts (all last scripts for release 2.14.2)

  * trunk/ - Here you will find all commits of scripts and patches wich will change more frequently.

  You can use the Tickets service available from [http://linux.redos.si/trac/report] and 
  from here [http://linux.redos.si/trac/newticket] . 

  ----
  = OpenOffice on Slackware with DroplineGNOME =
  If you are looking for '''OpenOffice.org''' build instructions for Slackware and DroplineGNOME please look [[wiki:OpenOffice.org here]]

  ----
  = Dropline Installer =
  For '''Dropline Installer''' please look [[wiki:DroplineInstaller here]]

  Enjoy
  Saxa


name: DroplineInstaller
author: anonymous
ipnr: 217.223.95.245
text:
  == Dropline Installer ==

  This should be an descriptionof how the Dropline Installer should work and what it should do.

  This page will have more details very soon :)
  Thanks for the initiative to Johnny Mast :)

  Rgds
  Saxa


  ----

  Ok lets begin from the beginning. So what the dropline installer should be. In the text I will use 
  DLGI abreviation for droplinegnome-installer.

  So DLGI is an app which runs on a Slackware system and helps you to install the GNOME desktop
  packaged by the DroplineGNOME team. 
  The DLGI should have the following functionalities:

  - Should run in a non X enviroment, this because we do not have always X installed on Slackware where we want to install DroplineGNOME.

  - Should run in a X graphical enviroment without GNOME installed. As slackware uses XFCE I beleave it can be written in GTK+.

  - Should run also in a GNOME enviroment.

  - Should check for updates of the new awailable packages we made available on sf.net and mirrors.

  - Should allow you to only download the the packages. 

  - Should allow you to install packages from a .iso we supply.

  - Should allow you to select a mirror from where to download the packages.

  ----
  Ok lets go to see how the installer should do all the tasks.

  === Non graphical enviroment: ===

  If we run the installer as a non root user it should warn you that you will not be able to install the packages untill you supply the root password, but it should allow you to download the packages of course storing them into users home dir and let you select the mirror. Same thing is for updating the system. If run as a non root user it should allow only to download the updates.

  Also it should check if we have all the required system components (kernel version, X enviroment, which libs, networking and so on). 

  We should have a sort of choosing option on which Slackware version we want to install the packages on. So if we choose Slackwares previous release it should automatically download the correct packages released for that Slackware release. 

  Example: Choose Slackware 10.2 -> installs DroplineGNOME 2.14.x 

  It should also allow you to install the various dot releases we had. 

  Example: Slackware 10.2 -> selects DroplineGNOME 2.14.0, 2.14.1, 2.14.2 or 2.14.3

  After we have seleceted the release of DroplineGNOME it should be able to supply us the list of the mirrors where the packages are available on. It can give us also an option to enter an URL of choice. When we selected the mirror
  It should check if it finds the correct DroplineFiles2.14 file where the packages are listed. If it does not find the file should wanr that without it it can install or cant continue and let us choose again.

  when we selected an mirror and it has all the data necessary it should ask if we want to download only the packages or if we want to install them also.

  After that the installer should look and download the DroplineFiles2.14 file and beguin downloading the packages
  from the selected mirror. 

  When downloading is finished it should check the downloaded packages integrity with the md5 files and if some package is broken it should redownload it, if everything is ok it should begin installing the packages according to the order listed in the DroplineFiles2.14 file.

  The DLGI should use the Slackwares pkgtools like installpkg, upgradepkg, removepkg.

  When it finishes to install it should ask the user if it wants to restart the sstem or only logout.

  The DLGI should also be able to change the inittab file in /etc to runlevel 4 so when we restart the machine after the sucessful installation we get the GDM page.

  Of course if the DLGI detects that the DroplineGNOME is already installed it should prompt the user what to do.
  The options can be Upgrade/Downgrade the system to a different version or Uninstall the DroplineGNOME Desktop.

  If the Uninstall option is choosen the DLGI should be able to restore the Slackware system according to the Slackware version installed.

  ----
  === Graphical mode: ===

  In the graphical mode the DLGI should act the same way as in the NON graphical mode except that it has a 
  frontend in GTK+.


  ----

  This is a raw description of how the installer should work.
  This information will be updated according to the necessarity during the coding of the installer.
  Written by Sasa Ostrouska 26-09-2006 , thats also my birthday :))
  ----

  = Drawings =
  ----
  http://developer.gnome.org/projects/gup/hig/
  = Stage 1: = 
  [[Image:Example.jpg]]


name: DroplineInstaller
author: anonymous
ipnr: 217.223.95.245
text:
  == Dropline Installer ==

  This should be an descriptionof how the Dropline Installer should work and what it should do.

  This page will have more details very soon :)
  Thanks for the initiative to Johnny Mast :)

  Rgds
  Saxa


  ----

  Ok lets begin from the beginning. So what the dropline installer should be. In the text I will use 
  DLGI abreviation for droplinegnome-installer.

  So DLGI is an app which runs on a Slackware system and helps you to install the GNOME desktop
  packaged by the DroplineGNOME team. 
  The DLGI should have the following functionalities:

  - Should run in a non X enviroment, this because we do not have always X installed on Slackware where we want to install DroplineGNOME.

  - Should run in a X graphical enviroment without GNOME installed. As slackware uses XFCE I beleave it can be written in GTK+.

  - Should run also in a GNOME enviroment.

  - Should check for updates of the new awailable packages we made available on sf.net and mirrors.

  - Should allow you to only download the the packages. 

  - Should allow you to install packages from a .iso we supply.

  - Should allow you to select a mirror from where to download the packages.

  ----
  Ok lets go to see how the installer should do all the tasks.

  === Non graphical enviroment: ===

  If we run the installer as a non root user it should warn you that you will not be able to install the packages untill you supply the root password, but it should allow you to download the packages of course storing them into users home dir and let you select the mirror. Same thing is for updating the system. If run as a non root user it should allow only to download the updates.

  Also it should check if we have all the required system components (kernel version, X enviroment, which libs, networking and so on). 

  We should have a sort of choosing option on which Slackware version we want to install the packages on. So if we choose Slackwares previous release it should automatically download the correct packages released for that Slackware release. 

  Example: Choose Slackware 10.2 -> installs DroplineGNOME 2.14.x 

  It should also allow you to install the various dot releases we had. 

  Example: Slackware 10.2 -> selects DroplineGNOME 2.14.0, 2.14.1, 2.14.2 or 2.14.3

  After we have seleceted the release of DroplineGNOME it should be able to supply us the list of the mirrors where the packages are available on. It can give us also an option to enter an URL of choice. When we selected the mirror
  It should check if it finds the correct DroplineFiles2.14 file where the packages are listed. If it does not find the file should wanr that without it it can install or cant continue and let us choose again.

  when we selected an mirror and it has all the data necessary it should ask if we want to download only the packages or if we want to install them also.

  After that the installer should look and download the DroplineFiles2.14 file and beguin downloading the packages
  from the selected mirror. 

  When downloading is finished it should check the downloaded packages integrity with the md5 files and if some package is broken it should redownload it, if everything is ok it should begin installing the packages according to the order listed in the DroplineFiles2.14 file.

  The DLGI should use the Slackwares pkgtools like installpkg, upgradepkg, removepkg.

  When it finishes to install it should ask the user if it wants to restart the sstem or only logout.

  The DLGI should also be able to change the inittab file in /etc to runlevel 4 so when we restart the machine after the sucessful installation we get the GDM page.

  Of course if the DLGI detects that the DroplineGNOME is already installed it should prompt the user what to do.
  The options can be Upgrade/Downgrade the system to a different version or Uninstall the DroplineGNOME Desktop.

  If the Uninstall option is choosen the DLGI should be able to restore the Slackware system according to the Slackware version installed.

  ----
  === Graphical mode: ===

  In the graphical mode the DLGI should act the same way as in the NON graphical mode except that it has a 
  frontend in GTK+.


  ----

  This is a raw description of how the installer should work.
  This information will be updated according to the necessarity during the coding of the installer.
  Written by Sasa Ostrouska 26-09-2006 , thats also my birthday :))
  ----

  = Drawings =



  = Stage 1: = 
  [[Image:Example.jpg]]


  ----
  http://developer.gnome.org/projects/gup/hig/



  = Engenering (By Johnny) =

  This is my point of view on the application conforming the gnome HIG (Human interface guide lines)

  End-Users
    * Desktop users
      * If they dont have a desktop yet console users.

  Applicatin Targets:
    * Could install from Desktop
    * Could install from console
    * Include language translations in the project.


name: OpenOffice.org64bit
author: sasa
ipnr: 217.223.95.244
text:
  === OpenOffice.org on a Slamd64-11.0 platform ===

  Tueseday, December 19th 2006

  == Getting the needed ==

  Ok here we go, the following parts are needed to get the OpenOffice.org to be built on a Slamd64-11.0 platform:

  - Slamd64-11.0 linux --> get it here: http://www.slamd64.com
  - Dropline GNOME 64bit --> get it from here: http://saxa.droplinegnome.org/x86_64/
  - ooo-build --> get it from here: http://go-oo.org/packages

  After you got all this, proceed with the next step :)

  == Preparing the enviroment ==

  Install Slamd64-11.0, install Dropline GNOME, after that you need to begin tweaking your system and its by doing the following:

  We need to install Ant first.

  We need some perl modules:
  In a virtual terminal issue the following command as root:
  # perl -MCPAN -e shell
  # install Archive::Zip


  == Building it from source == 


name: OpenOffice.org64bit
author: sasa
ipnr: 217.223.95.244
text:
  === OpenOffice.org on a Slamd64-11.0 platform ===

  Tueseday, December 19th 2006

  == Getting the needed ==

  Ok here we go, the following parts are needed to get the OpenOffice.org to be built on a Slamd64-11.0 platform:

  - Slamd64-11.0 linux --> get it here: http://www.slamd64.com

  - Dropline GNOME 64bit --> get it from here: http://saxa.droplinegnome.org/x86_64/

  - ooo-build --> get it from here: http://go-oo.org/packages


  After you got all this, proceed with the next step :)

  == Preparing the enviroment ==

  Install Slamd64-11.0, install Dropline GNOME, after that you need to begin tweaking your system and its by doing the following:

  We need to install Ant first.

  We need some perl modules:
  In a virtual terminal issue the following command as root:
  # perl -MCPAN -e shell
  # install Archive::Zip


  == Building it from source == 


name: OpenOffice.org64bit
author: sasa
ipnr: 217.223.95.244
text:
  === OpenOffice.org on a Slamd64-11.0 platform ===

  Tueseday, December 19th 2006

  == Getting the needed ==


  Ok here we go, the following parts are needed to get the OpenOffice.org to be built on a Slamd64-11.0 platform:

  - Slamd64-11.0 linux --> get it here: http://www.slamd64.com

  - Dropline GNOME 64bit --> get it from here: http://saxa.droplinegnome.org/x86_64/

  - ooo-build --> get it from here: http://go-oo.org/packages


  After you got all this, proceed with the next step :)



  == Preparing the enviroment ==


  Install Slamd64-11.0, install Dropline GNOME, after that you need to begin tweaking your system and its by doing the following:

  We need to install Ant first.

  We need some perl modules:
  In a virtual terminal issue the following command as root:
  # perl -MCPAN -e shell
  # install Archive::Zip


  == Building it from source == 


name: OpenOffice.org64bit
author: sasa
ipnr: 217.223.95.244
text:
  === '''OpenOffice.org on a Slamd64-11.0 platform''' ===

  Tueseday, December 19th 2006

  == Getting the needed ==


  Ok here we go, the following parts are needed to get the OpenOffice.org to be built on a Slamd64-11.0 platform:

  - Slamd64-11.0 linux --> get it here: http://www.slamd64.com

  - Dropline GNOME 64bit --> get it from here: http://saxa.droplinegnome.org/x86_64/

  - ooo-build --> get it from here: http://go-oo.org/packages


  After you got all this, proceed with the next step :)



  == Preparing the enviroment ==


  Install Slamd64-11.0, install Dropline GNOME, after that you need to begin tweaking your system and its by doing the following:

  We need to install Ant first.

  We need some perl modules:
  In a virtual terminal issue the following command as root:
  # perl -MCPAN -e shell
  # install Archive::Zip


  == Building it from source == 


name: OpenOffice.org64bit
author: sasa
ipnr: 217.223.95.244
text:
  === '''OpenOffice.org on a Slamd64-11.0 platform''' ===

  Tueseday, December 19th 2006

  == Getting the needed ==


  Ok here we go, the following parts are needed to get the OpenOffice.org to be built on a Slamd64-11.0 platform:

  - Slamd64-11.0 linux --> get it here: http://www.slamd64.com

  - Dropline GNOME 64bit --> get it from here: http://saxa.droplinegnome.org/x86_64/

  - ooo-build --> get it from here: http://go-oo.org/packages


  After you got all this, proceed with the next step :)



  == Preparing the enviroment ==


  Install Slamd64-11.0, install Dropline GNOME, after that you need to begin tweaking your system and its by doing the following:

  ''Step 1:''

  Install the java development kit, get it from here:

  http://ftp.scarlet.be/pub/slamd64/slamd64-11.0/extra/jdk/jdk-1_5_0_09-x86_64-1.tgz

  ''Step 2:''

  Install apache-ant

  We need to install Ant first.

  We need some perl modules:
  In a virtual terminal issue the following command as root:
  # perl -MCPAN -e shell
  # install Archive::Zip


  == Building it from source == 


name: OpenOffice.org64bit
author: sasa
ipnr: 217.223.95.244
text:
  === '''OpenOffice.org on a Slamd64-11.0 platform''' ===

  Tueseday, December 19th 2006

  == Getting the needed ==


  Ok here we go, the following parts are needed to get the OpenOffice.org to be built on a Slamd64-11.0 platform:

  - Slamd64-11.0 linux --> get it here: http://www.slamd64.com

  - Dropline GNOME 64bit --> get it from here: http://saxa.droplinegnome.org/x86_64/

  - ooo-build --> get it from here: http://go-oo.org/packages


  After you got all this, proceed with the next step :)



  == Preparing the enviroment ==


  Install Slamd64-11.0, install Dropline GNOME, after that you need to begin tweaking your system and its by doing the following:

  ''Step 1:''

  Install the java development kit, get it from here:

  http://ftp.scarlet.be/pub/slamd64/slamd64-11.0/extra/jdk/jdk-1_5_0_09-x86_64-1.tgz

  ''Step 2:''

  Install apache-ant which you can get here:

  http://apache.fis.uniroma2.it/ant/source/apache-ant-1.6.5-src.tar.bz2

  This is the source package, and you need to build it. To do so you can grab my slackbuild script from [[here]]

  ''Step 3:''

  We need some perl modules:
  In a virtual terminal issue the following command as root:
  # perl -MCPAN -e shell
  # install Archive::Zip


  == Building it from source == 


name: OpenOffice.org64bit
author: sasa
ipnr: 217.223.95.244
text:
  === '''OpenOffice.org on a Slamd64-11.0 platform''' ===

  Tueseday, December 19th 2006

  == Getting the needed ==


  Ok here we go, the following parts are needed to get the OpenOffice.org to be built on a Slamd64-11.0 platform:

  - Slamd64-11.0 linux --> get it here: http://www.slamd64.com

  - Dropline GNOME 64bit --> get it from here: http://saxa.droplinegnome.org/x86_64/

  - ooo-build --> get it from here: http://go-oo.org/packages


  After you got all this, proceed with the next step :)



  == Preparing the enviroment ==


  Install Slamd64-11.0, install Dropline GNOME, after that you need to begin tweaking your system and its by doing the following:

  ''Step 1:''

  Install the java development kit, get it from here:

  http://ftp.scarlet.be/pub/slamd64/slamd64-11.0/extra/jdk/jdk-1_5_0_09-x86_64-1.tgz

  ''Step 2:''

  Install apache-ant which you can get here:

  http://apache.fis.uniroma2.it/ant/source/apache-ant-1.6.5-src.tar.bz2

  This is the source package, and you need to build it. To do so you can grab my slackbuild script from [ *[ here ]* ]

  ''Step 3:''

  We need some perl modules:
  In a virtual terminal issue the following command as root:
  # perl -MCPAN -e shell
  # install Archive::Zip


  == Building it from source == 


name: OpenOffice.org64bit
author: sasa
ipnr: 217.223.95.244
text:
  === '''OpenOffice.org on a Slamd64-11.0 platform''' ===

  Tueseday, December 19th 2006

  == Getting the needed ==


  Ok here we go, the following parts are needed to get the OpenOffice.org to be built on a Slamd64-11.0 platform:

  - Slamd64-11.0 linux --> get it here: http://www.slamd64.com

  - Dropline GNOME 64bit --> get it from here: http://saxa.droplinegnome.org/x86_64/

  - ooo-build --> get it from here: http://go-oo.org/packages


  After you got all this, proceed with the next step :)



  == Preparing the enviroment ==


  Install Slamd64-11.0, install Dropline GNOME, after that you need to begin tweaking your system and its by doing the following:

  ''Step 1:''

  Install the java development kit, get it from here:

  http://ftp.scarlet.be/pub/slamd64/slamd64-11.0/extra/jdk/jdk-1_5_0_09-x86_64-1.tgz

  ''Step 2:''

  Install apache-ant which you can get here:

  http://apache.fis.uniroma2.it/ant/source/apache-ant-1.6.5-src.tar.bz2

  This is the source package, and you need to build it. To do so you can grab my slackbuild script from [ *[ here ]* ]

  ''Step 3:''

  We need some perl modules:

  In a virtual terminal issue the following command as root:

  # perl -MCPAN -e shell

  # install Archive::Zip


  == Building it from source == 


name: WikiStart
author: saxa
ipnr: 192.168.1.254
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  This will soon be more updated with various news and things I do over here.
  All the stuff for now is a bit experimental as I play with it.
  But soon when I realise how to do it well I will finish it and try to do a nice organised 
  site to have all the stuff usefull.

  So for now you can browse the dropline-build-system sources here [http://linux.redos.si/trac/browser]

  I will use the following directories and structure on the svn repository.

  * branches/ - This will be used for the scripts I upgrade to the current release

  * tags/ - Here will be the home of the last released scripts (all last scripts for release 2.14.2)

  * trunk/ - Here you will find all commits of scripts and patches wich will change more frequently.

  You can use the Tickets service available from [http://linux.redos.si/trac/report] and 
  from here [http://linux.redos.si/trac/newticket] . 

  ----
  = OpenOfficeOrg on Slackware with DroplineGNOME =
  If you are looking for '''[wiki:OpenOfficeOrg OpenOffice.org]''' build instructions for Slackware and DroplineGNOME please look [wiki:OpenOfficeOrg here]

  If you are looking for '''[wiki:OpenOfficeOrg64bit OpenOffice.org]''' build instructions for Slamd64 and DroplineGNOME please look [wiki:OpenOfficeOrg64bit here]

  ----
  = Dropline Installer =
  For '''Dropline Installer''' please look [[wiki:DroplineInstaller here]]

  Enjoy
  Saxa


name: PulseAudio-for-dlg
author: saxa
ipnr: 217.223.95.245
comment: Pulse Audio setup page created
text:
  == Pulse Audo for Dropline GNOME ==

  ---

  = The HOWTO for Pulse Audio on Slackware with Dropline GNOME =

  Ok on this page I will try to explain how to do and how to get [http://www.pulseaudio.org Pulse Audio] set up on a Slackware 12.0 system with Dropline GNOME 2.20.x.

  The following requirements must be met:

  - Slackware 12.0 with Dropline GNOME 2.20.x
  - libsamplerate
  - libsndfile
  - libatomic_ops

  The above dependencies must be installed before you can go ahead. If you don't have at least those the thing wont work for you.

   


name: PulseAudio-for-dlg
author: saxa
ipnr: 217.223.95.245
text:
  = Pulse Audo for Dropline GNOME =

  ------

  == The HOWTO for Pulse Audio on Slackware with Dropline GNOME ==

  Ok on this page I will try to explain how to do and how to get [http://www.pulseaudio.org Pulse Audio] set up on a Slackware 12.0 system with Dropline GNOME 2.20.x.

  The following requirements must be met:

  - Slackware 12.0 with Dropline GNOME 2.20.x
  - libsamplerate
  - libsndfile
  - libatomic_ops

  The above dependencies must be installed before you can go ahead. If you don't have at least those the thing wont work for you.

   


name: PulseAudio-for-dlg
author: anonymous
ipnr: 217.223.95.245
text:
  = Pulse Audo for Dropline GNOME =

  ------

  == The HOWTO for Pulse Audio on Slackware with Dropline GNOME ==

  Ok on this page I will try to explain how to do and how to get [http://www.pulseaudio.org Pulse Audio] set up on a Slackware 12.0 system with Dropline GNOME 2.20.x.

  The following requirements must be met:

  - Slackware 12.0 with Dropline GNOME 2.20.x

  - libsamplerate

  - libsndfile

  - libatomic_ops


  The above dependencies must be installed before you can go ahead. If you don't have at least those the thing wont work for you.

   


name: PulseAudio-for-dlg
author: anonymous
ipnr: 217.223.95.245
text:
  = Pulse Audo for Dropline GNOME =

  ------

  == The HOWTO for Pulse Audio on Slackware with Dropline GNOME ==

  Ok on this page I will try to explain how to do and how to get [http://www.pulseaudio.org Pulse Audio] set up on a Slackware 12.0 system with Dropline GNOME 2.20.x.

  The following requirements must be met:

  - Slackware 12.0 with Dropline GNOME 2.20.x

  - libsamplerate

  - libsndfile

  - libatomic_ops

  - libglademm (This is needed by pavucontrol gui)

  The above dependencies must be installed before you can go ahead. If you don't have at least those the thing wont work for you.

   


name: PulseAudio-for-dlg
author: anonymous
ipnr: 217.223.95.245
text:
  = Pulse Audo for Dropline GNOME =

  ------

  == The HOWTO for Pulse Audio on Slackware with Dropline GNOME ==

  Ok on this page I will try to explain how to do and how to get [http://www.pulseaudio.org Pulse Audio] set up on a Slackware 12.0 system with Dropline GNOME 2.20.x.

  The following requirements must be met:

  - Slackware 12.0 with Dropline GNOME 2.20.x

  - libsamplerate

  - libsndfile

  - libatomic_ops

  - libglademm (This is needed by pavucontrol gui)

  - gconfmm (This is required by paprefs gui)


  The above dependencies must be installed before you can go ahead. If you don't have at least those the thing wont work for you.

   


name: PulseAudio-for-dlg
author: saxa
ipnr: 217.223.95.245
text:
  = Pulse Audo for Dropline GNOME =

  ------

  == The HOWTO for Pulse Audio on Slackware with Dropline GNOME ==

  Ok on this page I will try to explain how to do and how to get [http://www.pulseaudio.org Pulse Audio] set up on a Slackware 12.0 system with Dropline GNOME 2.20.x.

  The following requirements must be met:
  {{{
  - Slackware 12.0 with Dropline GNOME 2.20.x
  - libsamplerate
  - libsndfile
  - libatomic_ops
  - libglademm (This is needed by pavucontrol gui)
  - gconfmm (This is required by paprefs gui)
  }}}

  The above dependencies must be installed before you can go ahead. If you don't have at least those the thing wont work for you.

   
  After that you can download the packages from the following directory and install them:

  '''Please note that those packages are for Slackware 12.0 and will NOT work on any other distro or Slackware version.'''

  http://saxa.droplinegnome.org/2.20.1/pulseaudio/

  When you have installed the packages you can begin experimenting with the pulseaudo server.

  Thats it for now. Thanks and enjoy.

  Saxa 


name: WikiStart
author: saxa
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  This will soon be more updated with various news and things I do over here.
  All the stuff for now is a bit experimental as I play with it.
  But soon when I realise how to do it well I will finish it and try to do a nice organised 
  site to have all the stuff usefull.

  So for now you can browse the dropline-build-system sources here [http://linux.redos.si/trac/browser]

  I will use the following directories and structure on the svn repository.

  * branches/ - This will be used for the scripts I upgrade to the current release

  * tags/ - Here will be the home of the last released scripts (all last scripts for release 2.14.2)

  * trunk/ - Here you will find all commits of scripts and patches wich will change more frequently.

  You can use the Tickets service available from [http://linux.redos.si/trac/report] and 
  from here [http://linux.redos.si/trac/newticket] . 

  ----
  = OpenOfficeOrg on Slackware with DroplineGNOME =
  If you are looking for '''[wiki:OpenOfficeOrg OpenOffice.org]''' build instructions for Slackware and DroplineGNOME please look [wiki:OpenOfficeOrg here]

  If you are looking for '''[wiki:OpenOfficeOrg64bit OpenOffice.org]''' build instructions for Slamd64 and DroplineGNOME please look [wiki:OpenOfficeOrg64bit here]

  ----
  = Dropline Installer =
  For '''Dropline Installer''' please look [[wiki:DroplineInstaller here]]

  ----
  = Pulse Audio on Slackware =
  For info please look at that [[wiki:PulseAudio-for-dlg page]]

  Enjoy
  Saxa


name: WikiStart
author: saxa
ipnr: 217.223.95.245
text:
  = Welcome to the Saxa's Dropline GNOME trac server =

  This will soon be more updated with various news and things I do over here.
  All the stuff for now is a bit experimental as I play with it.
  But soon when I realise how to do it well I will finish it and try to do a nice organised 
  site to have all the stuff usefull.

  So for now you can browse the dropline-build-system sources here [http://linux.redos.si/trac/browser]

  I will use the following directories and structure on the svn repository.

  * branches/ - This will be used for the scripts I upgrade to the current release

  * tags/ - Here will be the home of the last released scripts (all last scripts for release 2.14.2)

  * trunk/ - Here you will find all commits of scripts and patches wich will change more frequently.

  You can use the Tickets service available from [http://linux.redos.si/trac/report] and 
  from here [http://linux.redos.si/trac/newticket] . 

  ----
  = OpenOfficeOrg on Slackware with DroplineGNOME =
  If you are looking for '''[wiki:OpenOfficeOrg OpenOffice.org]''' build instructions for Slackware and DroplineGNOME please look [wiki:OpenOfficeOrg here]

  If you are looking for '''[wiki:OpenOfficeOrg64bit OpenOffice.org]''' build instructions for Slamd64 and DroplineGNOME please look [wiki:OpenOfficeOrg64bit here]

  ----
  = Dropline Installer =
  For '''Dropline Installer''' please look [wiki:DroplineInstaller here]

  ----
  = Pulse Audio on Slackware =
  For info please look at that [wiki:PulseAudio-for-dlg page]

  Enjoy
  Saxa


name: PulseAudio-for-dlg
author: saxa
ipnr: 217.223.95.242
text:
  = Pulse Audo for Dropline GNOME =

  This is a work in progress. Please be advised that its not finished.
  ------

  == The HOWTO for Pulse Audio on Slackware with Dropline GNOME ==

  Ok on this page I will try to explain how to do and how to get [http://www.pulseaudio.org Pulse Audio] set up on a Slackware 12.0 system with Dropline GNOME 2.20.x.

  The following requirements must be met:
  {{{
  - Slackware 12.0 with Dropline GNOME 2.20.x
  - libsamplerate
  - libsndfile
  - libatomic_ops
  - libglademm (This is needed by pavucontrol gui)
  - gconfmm (This is required by paprefs gui)
  }}}

  The above dependencies must be installed before you can go ahead. If you don't have at least those the thing wont work for you.

   
  After that you can download the packages from the following directory and install them:

  '''Please note that those packages are for Slackware 12.0 and will NOT work on any other distro or Slackware version.'''

  http://saxa.droplinegnome.org/2.20.1/pulseaudio/

  When you have installed the packages you can begin experimenting with the pulseaudo server.

  Thats it for now. Thanks and enjoy.

  Saxa 


name: PulseAudio-for-dlg
author: anonymous
ipnr: 217.223.95.245
text:
  = Pulse Audo for Dropline GNOME =

  This is a work in progress. Please be advised that its not finished.
  ------

  == The HOWTO for Pulse Audio on Slackware with Dropline GNOME ==

  Ok on this page I will try to explain how to do and how to get [http://www.pulseaudio.org Pulse Audio] set up on a Slackware 12.0 system with Dropline GNOME 2.20.x.

  The following requirements must be met:
  {{{
  - Slackware 12.0 with Dropline GNOME 2.20.x
  - libsamplerate
  - libsndfile
  - libatomic_ops
  - libglademm (This is needed by pavucontrol gui)
  - gconfmm (This is required by paprefs gui)
  }}}

  The above dependencies must be installed before you can go ahead. If you don't have at least those the thing wont work for you.

   
  After that you can download the packages from the following directory and install them:

  '''Please note that those packages are for Slackware 12.0 and will NOT work on any other distro or Slackware version.'''

  http://saxa.droplinegnome.org/2.20.1/pulseaudio/

  When you have installed the packages you can begin experimenting with the pulseaudo server.

  - create users & groups for pulseaudio
  - create tmpfs mount point , add to fstab the following
  {{{
  tmpfs     /dev/shm      tmpfs   defaults 0   0
  }}}

  - load pulseaudio as a daemon: pulseaudio --system=1 -D


  Thats it for now. Thanks and enjoy.

  Saxa 


name: PulseAudio-for-dlg
author: anonymous
ipnr: 217.223.95.245
text:
  = Pulse Audo for Dropline GNOME =

  This is a work in progress. Please be advised that its not finished.
  ------

  == The HOWTO for Pulse Audio on Slackware with Dropline GNOME ==

  Ok on this page I will try to explain how to do and how to get [http://www.pulseaudio.org Pulse Audio] set up on a Slackware 12.0 system with Dropline GNOME 2.20.x.

  The following requirements must be met:
  {{{
  - Slackware 12.0 with Dropline GNOME 2.20.x
  - libsamplerate
  - libsndfile
  - libatomic_ops
  - libglademm (This is needed by pavucontrol gui)
  - gconfmm (This is required by paprefs gui)
  }}}

  The above dependencies must be installed before you can go ahead. If you don't have at least those the thing wont work for you.

   
  After that you can download the packages from the following directory and install them:

  '''Please note that those packages are for Slackware 12.0 and will NOT work on any other distro or Slackware version.'''

  http://saxa.droplinegnome.org/2.20.1/pulseaudio/

  When you have installed the packages you can begin experimenting with the pulseaudo server.

  - create users & groups for pulseaudio
  - create tmpfs mount point , add to fstab the following
  {{{
  tmpfs     /dev/shm      tmpfs   defaults 0   0
  }}}

  - load pulseaudio as a daemon: pulseaudio --system=1 -D

  - rebuilt with pulse user and --with-*-group=audio

  Thats it for now. Thanks and enjoy.

  Saxa 


name: PulseAudio-for-dlg
author: saxa
ipnr: 217.223.95.245
text:
  = Pulse Audo for Dropline GNOME =

  This is a work in progress. Please be advised that its not finished.
  ------

  == The HOWTO for Pulse Audio on Slackware with Dropline GNOME ==

  Ok on this page I will try to explain how to do and how to get [http://www.pulseaudio.org Pulse Audio] set up on a Slackware 12.0 system with Dropline GNOME 2.20.x.

  The following requirements must be met:
  {{{
  - Slackware 12.0 with Dropline GNOME 2.20.x
  - libsamplerate
  - libsndfile
  - libatomic_ops
  - libglademm (This is needed by pavucontrol gui)
  - gconfmm (This is required by paprefs gui)
  }}}

  The above dependencies must be installed before you can go ahead. If you don't have at least those the thing wont work for you.

   
  After that you can download the packages from the following directory and install them:

  '''Please note that those packages are for Slackware 12.0 and will NOT work on any other distro or Slackware version.'''

  http://saxa.droplinegnome.org/2.20.1/pulseaudio/

  When you have installed the packages you can begin experimenting with the pulseaudo server.

  - create users & groups for pulseaudio
  {{{
  useradd -d /var/run/pulse -s /bin/false 
  }}}

  - create tmpfs mount point , add to fstab the following
  {{{
  tmpfs     /dev/shm      tmpfs   defaults 0   0
  }}}

  - load pulseaudio as a daemon: pulseaudio --system=1 -D

  - rebuilt with pulse user and --with-*-group=audio

  Thats it for now. Thanks and enjoy.

  Saxa 


name: CamelCase
author: trac
ipnr: 127.0.0.1
text:
  = !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.

  == Customizing the Wiki behavior ==

  Some people dislike linking by CamelCase.  While Trac remains faithful to the original Wiki style, it provides a number of ways to accomodate users with different preferences:
   * There's an option (`ignore_missing_pages` in `[wiki]`) to simply ignore links to missing pages when the link is written using the CamelCase style, instead of that word being replaced by a gray link followed by a question mark.[[BR]]
     That can be useful when CamelCase style is used to name code artifacts like class names and there's no corresponding page for them.
   * There's an option (`split_page_names` in `[wiki]`) to automatically insert space characters between the words of a CamelCase link when rendering the link.
   * Creation of explicit Wiki links is also easy, see WikiPageNames for details.
   * In addition, Wiki formatting can be disabled completely in some places (e.g. when rendering commit log messages)

  See TracIni for more information on the available options.

  == More information on !CamelCase ==

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

  ----
  See also: WikiPageNames, WikiNewPage, WikiFormatting, TracWiki


name: InterMapTxt
author: trac
ipnr: 127.0.0.1
text:
  = InterMapTxt =

  == This is the place for defining InterWiki prefixes ==

  This page was modelled after the MeatBall:InterMapTxt page.
  In addition, an optional comment is allowed after the mapping.


  This page is interpreted in a special way by Trac, in order to support
  !InterWiki links in a flexible and dynamic way.

  The code block after the first line separator in this page
  will be interpreted as a list of !InterWiki specifications:
  {{{
  prefix <space> URL [<space> # comment]
  }}}

  By using `$1`, `$2`, etc. within the URL, it is possible to create 
  InterWiki links which support multiple arguments, e.g. Trac:ticket:40.
  The URL itself can be optionally followed by a comment, 
  which will subsequently be used for decorating the links 
  using that prefix.

  New !InterWiki links can be created by adding to that list, in real time.
  Note however that ''deletions'' are also taken into account immediately,
  so it may be better to use comments for disabling prefixes.

  Also note that !InterWiki prefixes are case insensitive.


  == List of Active Prefixes ==

  [[InterWiki]]


  ----

  == Prefix Definitions ==

  {{{
  PEP     http://www.python.org/peps/pep-$1.html                                       # Python Enhancement Proposal 
  PythonBug http://bugs.python.org/issue$1                                             # Python Issue #$1
  Trac-ML  http://thread.gmane.org/gmane.comp.version-control.subversion.trac.general/ # Message $1 in Trac Mailing List
  trac-dev http://thread.gmane.org/gmane.comp.version-control.subversion.trac.devel/   # Message $1 in Trac Development Mailing List

  Mercurial http://www.selenic.com/mercurial/wiki/index.cgi/ # the wiki for the Mercurial distributed SCM
  RFC       http://tools.ietf.org/html/rfc$1 # IETF's RFC $1
  ISO       http://en.wikipedia.org/wiki/ISO_ # ISO Standard $1 in Wikipedia

  CheeseShop  http://cheeseshop.python.org/pypi/  # Python Package $1 from the Cheese Shop
  SQLite      http://www.sqlite.org/cvstrac/wiki?p= 
  mysql-bugs  http://bugs.mysql.com/bug.php?id=  # Bug #$1 in MySQL's bug database
  peak        http://peak.telecommunity.com/DevCenter/ # $1 in Python Enterprise Application Kit's Wiki
  MODPYTHON   http://issues.apache.org/jira/browse/MODPYTHON- # Issue $1 in mod_python's JIRA instance
  SvnWiki     http://www.orcaware.com/svn/wiki/ # Subversion Wiki

  #
  # A arbitrary pick of InterWiki prefixes...
  #
  Acronym          http://www.acronymfinder.com/af-query.asp?String=exact&Acronym=
  C2find           http://c2.com/cgi/wiki?FindPage&value=
  Cache            http://www.google.com/search?q=cache:
  CPAN             http://search.cpan.org/perldoc?
  DebianBug        http://bugs.debian.org/
  DebianPackage    http://packages.debian.org/
  Dictionary       http://www.dict.org/bin/Dict?Database=*&Form=Dict1&Strategy=*&Query=
  Google           http://www.google.com/search?q=
  GoogleGroups     http://groups.google.com/group/$1/msg/$2        # Message $2 in $1 Google Group
  JargonFile       http://downlode.org/perl/jargon-redirect.cgi?term=
  MeatBall         http://www.usemod.com/cgi-bin/mb.pl?
  MetaWiki         http://sunir.org/apps/meta.pl?
  MetaWikiPedia    http://meta.wikipedia.org/wiki/
  MoinMoin         http://moinmoin.wikiwikiweb.de/
  WhoIs            http://www.whois.sc/
  Why              http://clublet.com/c/c/why?
  c2Wiki             http://c2.com/cgi/wiki?
  WikiPedia        http://en.wikipedia.org/wiki/
  }}}


name: InterTrac
author: trac
ipnr: 127.0.0.1
text:
  = InterTrac Links  =

  Trac supports a convenient way to refer to resources of other Trac servers, from within the Wiki markup, since version 0.10.

  == Definitions ==

  An InterTrac link can be seen as a scoped TracLinks.
  It is used for referring to a Trac resource 
  (Wiki page, changeset, ticket, ...) located in another
  Trac environment.

  == List of Active InterTrac Prefixes ==

  [[InterTrac]]

  == Link Syntax ==

  Simply use the name of the other Trac environment as a prefix, 
  followed by a colon, ending with the resource located in the other environment.

  {{{
  <target_environment>:<TracLinks>
  }}}

  The other resource is specified using a regular TracLinks, of any flavor.

  That target environment name is either the real name of the 
  environment, or an alias for it. 
  The aliases are defined in `trac.ini` (see below).
  The prefix is case insensitive.

  For convenience, there's also some alternative short-hand form, 
  where one can use an alias as an immediate prefix 
  for the identifier of a ticket, changeset or report:
  (e.g. `#T234`, `[T1508]`, `[trac 1508]`, ...)

  == Examples ==

  It is necessary to setup a configuration for the InterTrac facility.
  This configuration has to be done in the TracIni file, `[intertrac]` section.

  Example configuration:
  {{{
  ...
  [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
  }}}

  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 will be used for providing an useful tooltip
  when moving the cursor over an InterTrac links.

  Finally, the `.compat` option can be used to activate or disable
  a ''compatibility'' mode:
   * If the targeted Trac is running a version below [trac:milestone:0.10 0.10] 
     ([trac:r3526 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 `true` 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 an InterTrac link.

  Now, given the above configuration, one could create the following links:
   * to this InterTrac page:
     * `trac:wiki:InterTrac` trac:wiki:InterTrac
     * `t:wiki:InterTrac` t:wiki:InterTrac
     * Keys are case insensitive: `T:wiki:InterTrac` T:wiki:InterTrac
   * to the ticket #234:
     * `trac:ticket:234` trac:ticket:234
     * `trac:#234` trac:#234 
     * `#T234` #T234
   * to the changeset [1912]:
     * `trac:changeset:1912` trac:changeset:1912
     * `[T1912]` [T1912]
   * to the log range [3300:3330]: '''(Note: the following ones need `trac.compat=false`)'''
     * `trac:log:@3300:3330` trac:log:@3300:3330  
     * `[trac 3300:3330]` [trac 3300:3330] 
   * finally, to link to the start page of a remote trac, simply use its prefix followed by ':', inside an explicit link. Example: `[th: Trac Hacks]` (''since 0.11; note that the ''remote'' Trac has to run 0.11 for this to work'')

  The generic form `intertrac_prefix:module:id` is translated
  to the corresponding URL `<remote>/module/id`, shorthand links
  are specific to some modules (e.g. !#T234 is processed by the
  ticket module) and for the rest (`intertrac_prefix:something`),
  we rely on the TracSearch#quickjump facility of the remote Trac.

  ----
  See also: TracLinks, InterWiki


name: InterWiki
author: trac
ipnr: 127.0.0.1
text:
  = Support for InterWiki links =

  ''(since [trac:milestone:0.10 0.10])''

  == Definition ==

  An InterWiki link can be used for referring to a Wiki page
  located in another Wiki system, and by extension, to any object
  located in any other Web application, provided a simple URL 
  mapping can be done.

  At the extreme, InterWiki prefixes can even be used to simply introduce
  links to new protocols, such as `tsvn:` used by [trac:TortoiseSvn TortoiseSvn].

  == Link Syntax ==

  {{{
  <target_wiki>(:<identifier>)+
  }}}

  The link is composed by the targeted Wiki (or system) name,
  followed by a colon (e.g. `MeatBall:`),
  followed by a page specification in the target.
  Note that, as for InterTrac prefixes, '''InterWiki prefixes are case insensitive'''.

  The target Wiki URL is looked up in the InterMapTxt wiki page, 
  modelled after MeatBall:InterMapTxt.

  In addition to traditional InterWiki links, where the target
  is simply ''appended'' to the URL, 
  Trac supports parametric InterWiki URLs:
  identifiers `$1`, `$2`, ... in the URL
  will be replaced by corresponding arguments.
  The argument list is formed by splitting the page identifier
  using the ":" separator.

  == Examples ==

  If the following is an excerpt of the InterMapTxt page:

  {{{
  = InterMapTxt =
  == This is the place for defining InterWiki prefixes ==

  Currently active prefixes: [[InterWiki]]

  This page is modelled after the MeatBall:InterMapTxt page.
  In addition, an optional comment is allowed after the mapping.
  ----
  {{{
  PEP      http://www.python.org/peps/pep-$1.html           # Python Enhancement Proposal $1 
  Trac-ML  http://thread.gmane.org/gmane.comp.version-control.subversion.trac.general/$1  # Message $1 in Trac Mailing List

  tsvn     tsvn:                                            # Interact with TortoiseSvn
  ...
  MeatBall http://www.usemod.com/cgi-bin/mb.pl?
  MetaWiki http://sunir.org/apps/meta.pl?
  MetaWikiPedia http://meta.wikipedia.org/wiki/
  MoinMoin http://moinmoin.wikiwikiweb.de/
  ...
  }}}
  }}}

  Then, 
   * `MoinMoin:InterWikiMap` should be rendered as MoinMoin:InterWikiMap
     and the ''title'' for that link would be "!InterWikiMap in !MoinMoin"
   * `Trac-ML:4346` should be rendered as Trac-ML:4346
     and the ''title'' for that link would be "Message 4346 in Trac Mailing List"

  ----
  See also: InterTrac, InterMapTxt


name: PageTemplates
author: trac
ipnr: 127.0.0.1
text:
  = Wiki Page Templates = 

    ''(since [http://trac.edgewall.org/milestone/0.11 0.11])''

  The default content for a new wiki page can be chosen from a list of page templates. 

  That list is made up from all the existing wiki pages having a name starting with ''PageTemplates/''.
  The initial content of a new page will simply be the content of the chosen template page, or a blank page if the special ''(blank page)'' entry is selected. When there's actually no wiki pages matching that prefix, the initial content will always be the blank page and the list selector will not be shown (i.e. this matches the behavior we had up to now).

  To create a new template, simply create a new page having a name starting with ''PageTemplates/''.

  (Hint: one could even create a ''!PageTemplates/Template'' for facilitating the creation of new templates!)

  Available templates:
  [[TitleIndex(PageTemplates/)]]

  ----
  See also: TracWiki


name: TracAccessibility
author: trac
ipnr: 127.0.0.1
text:
  = 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.''[[BR]]
  ''Note that when using Firefox 2.0 on Windows, you need to hit `<Shift> + <Alt> + <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
   * `e` - Edit this page
   * `f` - Search


  ----
  See also: TracGuide


name: TracAdmin
author: trac
ipnr: 127.0.0.1
text:
  = 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.

  Some of those operations can also be performed via the ''Admin'' web interface, an updated version of the [http://trac.edgewall.org/wiki/WebAdmin WebAdmin] plugin now integrated within Trac (since version 0.11).

  == 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 all the Wiki-related commands, run:
  {{{
  > help wiki
  }}}

  == Full Command Reference ==

  [[TracAdminHelp()]]


  === Notes ===

  The `initenv` also supports an extra `--inherit` option, which can be used to specify the `[inherit] file` option at environment creation time so that only the options ''not'' already specified in the global configuration file will be written in the conf/trac.ini file of the newly created environment.
  See TracIni#GlobalConfiguration.

  Note that in version 0.11 of Trac, `initenv` lost an extra last argument `<templatepath>`, which was used in previous versions to point to the `templates` folder. If you are using the one-liner '`trac-admin /path/to/trac/ initenv <projectname> <db> <repostype> <repospath>`' in the above and getting an error that reads ''''`Wrong number of arguments to initenv: 4`'''', then this is because you're using a `trac-admin` script from an '''older''' version of Trac.

  ----
  See also: TracGuide, TracBackup, TracPermissions, TracEnvironment, TracIni, [trac:TracMigrate TracMigrate]


name: TracBackup
author: trac
ipnr: 127.0.0.1
text:
  = 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`.

  Please, note, that hotcopy command does not overwrite target directory and when such exists, hotcopy ends with error: `Command failed: [Errno 17] File exists:` This is discussed in [trac:ticket:3198 #3198].

  === 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, TracMigrate


name: TracBrowser
author: trac
ipnr: 127.0.0.1
text:
  = The Trac Repository Browser =
  [[TracGuideToc]]

  The Trac repository browser can be used to browse directories 
  and specific revisions of files stored in the repository of the configured
  version control system.

  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 TracRevisionLog for that file.
  Note that there's also a ''Revision Log'' navigation link that will do
  the same for the path currently being examined.

  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.

  ''(since 0.11)'':

  The color bar next to the Age column gives a visual indication of the age
  of the last change to a file or directory. In the default configuration,
  blue is older and red is newer, but this can be [TracIni#browser-section configured].

  At the top of the browser page, there's a drop-down menu which you can use 
  to select some interesting places in the repository, for example branches or tags. 
  This is sometimes referred to as the ''browser quickjump'' facility.
  The precise meaning and content of this menu depends on your backend.
  For Subversion, this list contains by default a few branches (`trunk` and any sub-folder of the latest `branches` top-level folder) and a few tags (any sub-folder of the latest `tags` top-level folder). This can be [TracIni#svn-section configured] for more advanced cases.

  If you're using a Javascript enabled brower, you'll be able to expand and collapse folders in-place by clicking on the arrow head at the right side of a folder. Alternatively, the [trac:TracKeys keyboard] can also be used for this: use 'j' and 'k' to go to the next or previous entry, and 'o' (or 'Enter') to toggle between expanded and collapsed state of the selected folder or for visiting the selected file.

  For the Subversion backend, some additional features are available:
   - Support for the `svn:needs-lock` property
   - Support for the `svn:externals` property (which can be [TracIni#svn:externals-section configured])
   - The `svn:mime-type` property is used to select the syntax highlighter for rendering the file. For example, setting `svn:mime-type` to `text/html` will ensure the file is highlighted as HTML, regardless of the file extension. It also allows selecting the character encoding used in the file content. For example, if the file content is encoded in UTF-8, set `svn:mime-type` to `text/html;charset=utf-8`. The `charset=` specification overrides the default encoding defined in the `default_charset` option of the `[trac]` section of [TracIni#trac-section trac.ini].

  ----
  See also: TracGuide, TracChangeset, TracFineGrainedPermissions


name: TracCgi
author: trac
ipnr: 127.0.0.1
text:
  = 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.

  {{{
  #!div class=important
    ''Please note that using Trac via CGI is significantly slower than any other deployment method, such as [TracModPython mod_python] or [TracFastCgi FastCGI] or even [trac:TracOnWindowsIisAjp IIS/AJP] on Windows.''
  }}}

  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`). A word of warning, copying the file directly from the repository onto a windows server 2003 machine created difficulties. Rather create a new text file and cut and copy the text into the newly created file. 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
  }}}

   ''Note that this directive requires the `mod_alias` module to be installed and enabled.''

  If you're using Trac with a single project you need to set its location using the `TRAC_ENV` environment variable:
  {{{
  <Location "/trac">
    SetEnv TRAC_ENV "/path/to/projectenv"
  </Location>
  }}}

  Or to use multiple projects you can specify their common parent directory using the `TRAC_ENV_PARENT_DIR` variable:
  {{{
  <Location "/trac">
    SetEnv TRAC_ENV_PARENT_DIR "/path/to/project/parent/dir"
  </Location>
  }}}

   ''Note that the `SetEnv` directive requires the `mod_env` module to be installed and enable. If not, you could set TRAC_ENV in trac.cgi. Just add the following code between "try:" and "from trac.web ...":''

  {{{
      import os
      os.environ['TRAC_ENV'] = "/path/to/projectenv"
  }}}

   '' Or for TRAC_ENV_PARENT_DIR: ''

  {{{
      import os
      os.environ['TRAC_ENV_PARENT_DIR'] = "/path/to/project/parent/dir"
  }}}

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

  If you are using the [http://httpd.apache.org/docs/suexec.html Apache suEXEC] feature please see [http://trac.edgewall.org/wiki/ApacheSuexec].

  On some systems, you ''may'' need to edit the shebang line in the `trac.cgi` file to point to your real Python installation path. On a Windows system you may need to configure Windows to know how to execute a .cgi file (Explorer -> Tools -> Folder Options -> File Types -> CGI).

  == 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 much more efficiently served by the web server directly.

  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`.

  Similarly, if you have static resources in a projects htdocs directory, you can configure apache to serve those resources (again, put this '''before''' the `ScriptAlias` for the CGI script, and adjust names and locations to match your installation):

  {{{
  Alias /trac/chrome/site /path/to/projectenv/htdocs
  <Directory "/path/to/projectenv/htdocs">
    Order allow,deny
    Allow from all
  </Directory>
  }}}

  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:
  {{{
  $ ln -s /usr/share/trac/htdocs /var/www/your_site.com/htdocs/trac-htdocs
  }}}

  Note that in order to get this `htdocs` directory, you need first to extract the relevant Trac resources using the `deploy` command of TracAdmin:
  [[TracAdminHelp(deploy)]]


  == 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 "/trac/login">
    AuthType Basic
    AuthName "Trac"
    AuthUserFile /somewhere/trac.htpasswd
    Require valid-user
  </Location>
  }}}

  If you're hosting multiple projects you can use the same password file for all of them:
  {{{
  <LocationMatch "/trac/[^/]+/login">
    AuthType Basic
    AuthName "Trac"
    AuthUserFile /somewhere/trac.htpasswd
    Require valid-user
  </LocationMatch>
  }}}

  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. For example, on a Debian 4.0r1 (etch) system the relevant section  in apache configuration can look like this:
  {{{
  <Location "/trac/login">
      LoadModule auth_digest_module /usr/lib/apache2/modules/mod_auth_digest.so
      AuthType Digest
      AuthName "trac"
      AuthDigestDomain /trac
      AuthUserFile /somewhere/trac.htpasswd
      Require valid-user
  </Location>
  }}}
  and you'll have to create your .htpasswd file with htdigest instead of htpasswd as follows:
  {{{
  # htdigest /somewhere/trac.htpasswd trac admin
  }}}
  where the "trac" parameter above is the same as !AuthName above  ("Realm" in apache-docs). 

  ----
  See also:  TracGuide, TracInstall, wiki:TracModWSGI, TracFastCgi, TracModPython


name: TracChangeset
author: trac
ipnr: 127.0.0.1
text:
  = Trac Changeset Module =
  [[TracGuideToc]]

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

  There are different kinds of ''change sets''. 
  Some can correspond to revisions made in the repositories,
  others can aggregate changes made in several revisions, 
  but in the end, any kind of differences can be shown.

  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

  If more than one revision is involved in the set of changes being
  displayed, the ''Timestamp'', ''Author'' and ''Message'' fields 
  won't be shown.

  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
     (if the value ''all'' is used, then the full file will be shown)
   * You can toggle whether blank lines, case changes and white space changes are ignored, thereby letting you find the functional changes more quickly


  == The Different Ways to Get a Diff ==

  === Examining a Changeset ===

  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.

  There will be also navigation links to the ''Previous Changeset''
  to and ''Next Changeset''.

  === Examining Differences Between Revisions ===

  Often you'll want to look at changes made on a file 
  or on a directory spanning multiple revisions. The easiest way
  to get there is from the TracRevisionLog, where you can select
  the ''old'' and the ''new'' revisions of the file or directory, and
  then click the ''View changes'' button.

  === Examining Differences Between Branches ===

  One of the core features of version control systems is the possibility
  to work simultaneously on different ''Lines of Developments'', commonly
  called “branches”. Trac enables you to examine the exact differences
  between such branches.

  Using the '''View changes ...''' button in the TracBrowser allows you to enter
  ''From:'' and ''To:'' path/revision pairs. The resulting set of differences consist
  of the changes that should be applied to the ''From:'' content in order
  to get to the ''To:'' content.

  For convenience, it is possible to invert the roles of the ''old'' and the ''new''
  path/revision pairs by clicking the ''Reverse Diff'' link on the changeset page.

  === Checking the Last Change ===

  The last possibility for examining changes is to use the ''Last Change''
  link provided by the TracBrowser.

  This link will take you to the last change that was made on that path.
  From there, you can use the ''Previous Change'' and ''Next Change'' links
  to traverse the change history of the file or directory.

  ----
  See also: TracGuide, TracBrowser


name: TracEnvironment
author: trac
ipnr: 127.0.0.1
text:
  = The Trac Environment =

  Trac uses a directory structure and a database for storing project data. The directory is referred to as the “environment”.

  == Creating an Environment ==

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

  [wiki:TracAdmin trac-admin] will ask you for the name of the project, the
  database connection string (explained below), and the type and path to
  your source code repository.

  ''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 
  Trac is eventually using, although Trac will only require read access as long 
  as you're not using the BDB file system. Also, it seems that project names
  with spaces can be problematic for authentication (see [trac:#7163]).''

  == Database Connection Strings ==

  Since version 0.9, Trac supports both [http://sqlite.org/ SQLite] and
  [http://www.postgresql.org/ PostgreSQL] database backends.  Preliminary
  support for [http://mysql.com/ MySQL] was added in 0.10.  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.

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

  === PostgreSQL Connection String ===
  If you want to use PostgreSQL or MySQL instead, you'll have to use a
  different connection string. For example, to connect to a PostgreSQL
  database on the same machine called `trac`, that allows access to the
  user `johndoe` with the password `letmein`, use:
  {{{
  postgres://johndoe:letmein@localhost/trac
  }}}
  ''Note that due to the way the above string is parsed, the "/" and "@" characters cannot be part of the password.''

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

  On UNIX, you might want to select a UNIX socket for the transport,
  either the default socket as defined by the PGHOST environment variable:
  {{{
  postgres://user:password@/database
  }}}
  or a specific one:
  {{{
  postgres://user:password@/database?host=/path/to/socket/dir
  }}}

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

  See the [http://www.postgresql.org/docs/ PostgreSQL documentation] for detailed instructions on how to administer [http://postgresql.org PostgreSQL].
  Generally, the following is sufficient to create a database user named `tracuser`, and a database named `trac`.
  {{{
  createuser -U postgres -E -P tracuser
  createdb -U postgres -O tracuser -E UTF8 trac
  }}}
  When running `createuser` you will be prompted for the password for the user 'tracuser'. This new user will not be a superuser, will not be allowed to create other databases and will not be allowed to create other roles. These privileges are not needed to run a trac instance. If no password is desired for the user, simply remove the `-P` and `-E` options from the `createuser` command.  Also note that the database should be created as UTF8. LATIN1 encoding causes errors trac's use of unicode in trac.  SQL_ASCII also seems to work.

  Under some default configurations (debian) one will have run the `createuser` and `createdb` scripts as the `postgres` user.  For example:
  {{{
  sudo su - postgres -c 'createuser -U postgres -S -D -R -E -P tracuser'
  sudo su - postgres -c 'createdb -U postgres -O tracuser -E UTF8 trac'
  }}}

  Trac uses the `public` schema by default but you can specify a different schema in the connection string:
  {{{
  postgres://user:pass@server/database?schema=yourschemaname
  }}}

  === MySQL Connection String ===

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

  == Source Code Repository ==

  You'll first have to provide the ''type'' of your repository (e.g. `svn` for Subversion,
  which is the default), then the ''path'' where the repository is located.

  If you don't want to use Trac with a source code repository, simply leave the ''path'' empty
  (the ''type'' information doesn't matter, then).

  For some systems, it is possible to specify not only the path to the repository,
  but also a ''scope'' within the repository. Trac will then only show information
  related to the files and changesets below that scope. The Subversion backend for
  Trac supports this; for other types, check the corresponding plugin's documentation.

  Example of a configuration for a Subversion repository:
  {{{
  [trac]
  repository_type = svn
  repository_dir = /path/to/your/repository
  }}}

  The configuration for a scoped Subversion repository would be:
  {{{
  [trac]
  repository_type = svn
  repository_dir = /path/to/your/repository/scope/within/repos
  }}}

  == 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).
   * `htdocs` - directory containing web resources, which can be referenced in Genshi templates. '''''(0.11 only)'''''
   * `log` - default directory for log files, if logging is turned on and a relative path is given.
   * `plugins` - Environment-specific [wiki:TracPlugins plugins] (Python eggs, since [trac:milestone:0.10 0.10])
   * `templates` - Custom Genshi environment-specific templates. '''''(0.11 only)'''''
     * `site.html` - method to customize header, footer, and style, described in TracInterfaceCustomization#SiteAppearance
   * ''`templates` - Custom [trac:ClearSilver ClearSilver] environment-specific templates. '''(0.10 only)''' ''
     * ''`site_css.cs` - Custom CSS rules.''
     * ''`site_footer.cs` - Custom page footer.''
     * ''`site_header.cs` - Custom page header.''
   * ''`wiki-macros` - Environment-specific [WikiMacros Wiki macros]. '''(0.10 only)''' ''

    '''Note: don't confuse a Trac environment directory with the source code repository directory.
  It happens that the above structure is loosely modelled after the Subversion repository directory 
  structure, but they are not and ''must not'' be located at the same place.'''

  ----
  See also: TracAdmin, TracBackup, TracIni, TracGuide


name: TracFastCgi
author: trac
ipnr: 127.0.0.1
text:
  = 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.

  '''Note for Windows:''' Trac's FCGI does not run under Windows, as Windows does not implement `Socket.fromfd`, which is used by `_fcgi.py`. If you want to connect to IIS, your choice may be [trac:TracOnWindowsIisAjp AJP].

  == Simple Apache configuration ==

  There are two FastCGI modules commonly available for Apache: `mod_fastcgi` and
  `mod_fcgid`.  The `FastCgiIpcDir` and `FastCgiConfig` directives discussed
  below are `mod_fastcgi` directives; the `DefaultInitEnv` is a `mod_fcgid`
  directive.

  For `mod_fastcgi`, add the following to an appropriate Apache configuration
  file:
  {{{
  # 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
  }}}
  Setting `FastCgiIpcDir` is optional if the default is suitable. Note that the `LoadModule` line must be after the `IfModule` group.

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

  You can set up 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
  }}}

  But neither of these will work for `mod_fcgid`.  A similar but partial
  solution for `mod_fcgid` is:
  {{{
  DefaultInitEnv TRAC_ENV /path/to/env/trac/
  }}}
  But this cannot be used in `Directory` or `Location` context, which makes it
  difficult to support multiple projects.

  A better method which works for both of these modules (and for  [http://www.lighttpd.net/ lighttpd] and CGI as well), because it involves
  no server configuration settings for environment variables, is to set one
  of the variables in `trac.fcgi`, e.g.:
  {{{
  import os
  os.environ['TRAC_ENV'] = "/path/to/projectenv"
  }}}
  or
  {{{
  import os
  os.environ['TRAC_ENV_PARENT_DIR'] = "/path/to/project/parent/dir"
  }}}

  Using this method, different projects can be supported by using different
  `.fcgi` scripts with different `ScriptAliases`, copying and appropriately
  renaming `trac.fcgi` and adding the above code to create each such script.

  See [https://coderanger.net/~coderanger/httpd/fcgi_example.conf this fcgid example config] which uses a !ScriptAlias directive with trac.fcgi with a trailing / like this:
  {{{
  ScriptAlias / /srv/tracsite/cgi-bin/trac.fcgi/
  }}}

  == Simple Cherokee Configuration ==

  The configuration on Cherokee's side is quite simple. You will only need to know that you can spawn Trac as an SCGI process.
  You can either start it manually, or better yet, automatically by letting Cherokee spawn the server whenever it is down.
  First set up an information source in cherokee-admin with a local interpreter.

  {{{
  Host:
  localhost:4433

  Interpreter:
  /usr/bin/tracd —single-env —daemonize —protocol=scgi —hostname=localhost —port=4433 /path/to/project/
  }}}

  If the port was not reachable, the interpreter command would be launched. Note that, in the definition of the information source, you will have to manually launch the spawner if you use a ''Remote host'' as ''Information source'' instead of a ''Local interpreter''.

  After doing this, we will just have to create a new rule managed by the SCGI handler to access Trac. It can be created in a new virtual server, trac.example.net for instance, and will only need two rules. The '''default''' one will use the SCGI handler associated to the previously created information source.
  The second rule will be there to serve the few static files needed to correctly display the Trac interface. Create it as ''Directory rule'' for ''/chrome/common'' and just set it to the ''Static files'' handler and with a ''Document root'' that points to the appropriate files: ''/usr/share/trac/htdocs/''

  == 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`(prior to 0.11) / fcgi_frontend.py (0.11) with lighttpd add the following to your lighttpd.conf:
  {{{
  #var.fcgi_binary="/path/to/fcgi_frontend.py" # 0.11 if installed with easy_setup, it is inside the egg directory
  var.fcgi_binary="/path/to/cgi-bin/trac.fcgi" # 0.10 name of prior fcgi executable
  fastcgi.server = ("/trac" =>
     
                     ("trac" =>
                       ("socket" => "/tmp/trac-fastcgi.sock",
                        "bin-path" => fcgi_binary,
                        "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,
  and you may set one of the two in `trac.fcgi` instead of in `lighttpd.conf`
  using `bin-environment` (as in the section above on Apache configuration).

  For using two projects with lighttpd add the following to your `lighttpd.conf`:
  {{{
  fastcgi.server = ("/first" =>
                     ("first" =>
                      ("socket" => "/tmp/trac-fastcgi-first.sock",
                       "bin-path" => fcgi_binary,
                       "check-local" => "disable",
                       "bin-environment" =>
                         ("TRAC_ENV" => "/path/to/projenv-first")
                      )
                    ),
                    "/second" =>
                      ("second" =>
                      ("socket" => "/tmp/trac-fastcgi-second.sock",
                       "bin-path" => fcgi_binary,
                       "check-local" => "disable",
                       "bin-environment" =>
                         ("TRAC_ENV" => "/path/to/projenv-second")
                      )
                    )
                  )
  }}}
  Note that field values are different.  If you prefer setting the environment
  variables in the `.fcgi` scripts, then copy/rename `trac.fcgi`, e.g., to
  `first.fcgi` and `second.fcgi`, and reference them in the above settings.
  Note that the above will result in different processes in any event, even
  if both are running from the same `trac.fcgi` script.
  {{{
  #!div class=important
  '''Note''' It's very important the order on which server.modules are loaded, if mod_auth is not loaded '''BEFORE''' mod_fastcgi, then the server will fail to authenticate the user.
  }}}
  For authentication you should enable mod_auth in lighttpd.conf 'server.modules', select auth.backend and auth rules:
  {{{
  server.modules              = (
  ...
    "mod_auth",
  ...
  )

  auth.backend               = "htpasswd"

  # Separated password files for each project
  # See "Conditional Configuration" in
  # http://trac.lighttpd.net/trac/file/branches/lighttpd-merge-1.4.x/doc/configuration.txt

  $HTTP["url"] =~ "^/first/" {
    auth.backend.htpasswd.userfile = "/path/to/projenv-first/htpasswd.htaccess"
  }
  $HTTP["url"] =~ "^/second/" {
    auth.backend.htpasswd.userfile = "/path/to/projenv-second/htpasswd.htaccess"
  }

  # Enable auth on trac URLs, see
  # http://trac.lighttpd.net/trac/file/branches/lighttpd-merge-1.4.x/doc/authentication.txt

  auth.require = ("/first/login" =>
                  ("method"  => "basic",
                   "realm"   => "First project",
                   "require" => "valid-user"
                  ),
                  "/second/login" =>
                  ("method"  => "basic",
                   "realm"   => "Second project",
                   "require" => "valid-user"
                  )
                 )


  }}}
  Note that lighttpd (I use version 1.4.3) stopped if password file doesn't exist.

  Note that lighttpd doesn't support 'valid-user' in versions prior to 1.3.16.

  Conditional configuration is also useful for mapping static resources, i.e. serving out images and CSS directly instead of through FastCGI:
  {{{
  # Aliasing functionality is needed
  server.modules += ("mod_alias")

  # Setup an alias for the static resources
  alias.url = ("/trac/chrome/common" => "/usr/share/trac/htdocs")

  # Use negative lookahead, matching all requests that ask for any resource under /trac, EXCEPT in
  # /trac/chrome/common, and use FastCGI for those
  $HTTP["url"] =~ "^/trac(?!/chrome/common)" {
  # Even if you have other fastcgi.server declarations for applications other than Trac, do NOT use += here
  fastcgi.server = ("/trac" =>
                     ("trac" =>
                       ("socket" => "/tmp/trac-fastcgi.sock",
                        "bin-path" => fcgi_binary,
                        "check-local" => "disable",
                        "bin-environment" =>
                          ("TRAC_ENV" => "/path/to/projenv")
                       )
                     )
                   )
  }
  }}}
  The technique can be easily adapted for use with multiple projects by creating aliases for each of them, and wrapping the fastcgi.server declarations inside conditional configuration blocks.
  Also there is another way to handle multiple projects and it's to use TRAC_ENV_PARENT_DIR instead of TRAC_ENV and use global auth, let's see an example:
  {{{
  #  This is for handling multiple projects
    alias.url       = ( "/trac/" => "/path/to/trac/htdocs/" )

    fastcgi.server += ("/projects"  =>
                        ("trac" =>
                          (
                            "socket" => "/tmp/trac.sock",
                            "bin-path" => fcgi_binary,
                            "check-local" => "disable",
                            "bin-environment" =>
                              ("TRAC_ENV_PARENT_DIR" => "/path/to/parent/dir/of/projects/" )
                          )
                        )
                      )
  #And here starts the global auth configuration
    auth.backend = "htpasswd"
    auth.backend.htpasswd.userfile = "/path/to/unique/htpassword/file/trac.htpasswd"
    $HTTP["url"] =~ "^/projects/.*/login$" {
      auth.require = ("/" =>
                       (
                         "method"  => "basic",
                         "realm"   => "trac",
                         "require" => "valid-user"
                       )
                     )
    }
  }}}

  Changing date/time format also supported by lighttpd over environment variable LC_TIME
  {{{
  fastcgi.server = ("/trac" =>
                     ("trac" =>
                       ("socket" => "/tmp/trac-fastcgi.sock",
                        "bin-path" => fcgi_binary,
                        "check-local" => "disable",
                        "bin-environment" =>
                          ("TRAC_ENV" => "/path/to/projenv",
                          "LC_TIME" => "ru_RU")
                       )
                     )
                   )
  }}}
  For details about languages specification see [trac:TracFaq TracFaq] question 2.13.

  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.

  If you use trac-0.9, read [http://lists.edgewall.com/archive/trac/2005-November/005311.html about small bug]

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

  Note about running lighttpd with reduced permissions:

    If nothing else helps and trac.fcgi doesn't start with lighttpd settings __server.username = "www-data"__, __server.groupname = "www-data"__, then in the `bin-environment` section set `PYTHON_EGG_CACHE` to the home directory of `www-data` or some other directory accessible to this account for writing.


  == Simple !LiteSpeed Configuration ==

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

  !LiteSpeed web server is an event-driven asynchronous Apache replacement designed from the ground-up to be secure, scalable, and operate with minimal resources. !LiteSpeed can operate directly from an Apache config file and is targeted for business-critical environments.

  Setup

  1) Please make sure you have first have a working install of a Trac project. Test install with “tracd” first.

  2) Create a Virtual Host for this setup. From now on we will refer to this vhost as TracVhost. For this tutorial we will be assuming that your trac project will be accessible via:

  {{{
  http://yourdomain.com/trac/
  }}}

  3) Go “TracVhost → External Apps” tab and create a new “External Application”.

  {{{
  Name: MyTracFCGI	
  Address: uds://tmp/lshttpd/mytracfcgi.sock
  Max Connections: 10
  Environment: TRAC_ENV=/fullpathto/mytracproject/ <--- path to root folder of trac project
  Initial Request Timeout (secs): 30
  Retry Timeout (secs): 0
  Persistent Connection	Yes
  Connection Keepalive Timeout: 30
  Response Bufferring: No	
  Auto Start: Yes
  Command: /usr/share/trac/cgi-bin/trac.fcgi  <--- path to trac.fcgi
  Back Log: 50
  Instances: 10
  }}}

  4) Optional. If you need to use htpasswd based authentication. Go to “TracVhost → Security” tab and create a new security “Realm”.

  {{{
  DB Type: Password File
  Realm Name: MyTracUserDB               <--- any name you wish and referenced later
  User DB Location: /fullpathto/htpasswd <--- path to your htpasswd file
  }}}

  If you don’t have a htpasswd file or don’t know how to create the entries within one, go to http://sherylcanter.com/encrypt.php, to generate the user:password combos.

  5) Go to “PythonVhost → Contexts” and create a new “FCGI Context”.

  {{{
  URI: /trac/                              <--- URI path to bind to python fcgi app we created	
  Fast CGI App: [VHost Level] MyTractFCGI  <--- select the trac fcgi extapp we just created
  Realm: TracUserDB                        <--- only if (4) is set. select realm created in (4)
  }}}

  6) Modify /fullpathto/mytracproject/conf/trac.ini

  {{{
  #find/set base_rul, url, and link variables
  base_url = http://yourdomain.com/trac/ <--- base url to generate correct links to
  url = http://yourdomain.com/trac/      <--- link of project
  link = http://yourdomain.com/trac/     <--- link of graphic logo
  }}}

  7) Restart !LiteSpeed, “lswsctrl restart”, and access your new Trac project at: 

  {{{
  http://yourdomain.com/trac/
  }}}

  === Simple Nginx Configuration ===

  1) Nginx configuration snippet - confirmed to work on 0.6.32
  {{{
      server {
          listen       10.9.8.7:443;
          server_name  trac.example;

          ssl                  on;
          ssl_certificate      /etc/ssl/trac.example.crt;
          ssl_certificate_key  /etc/ssl/trac.example.key;

          ssl_session_timeout  5m;

          ssl_protocols  SSLv2 SSLv3 TLSv1;
          ssl_ciphers  ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP;
          ssl_prefer_server_ciphers   on;

          # (Or ``^/some/prefix/(.*)``.
          if ($uri ~ ^/(.*)) {
               set $path_info /$1;
          }

          # You can copy this whole location to ``location [/some/prefix]/login``
          # and remove the auth entries below if you want Trac to enforce
          # authorization where appropriate instead of needing to authenticate
          # for accessing the whole site.
          # (Or ``location /some/prefix``.)
          location / {
              auth_basic            "trac realm";
              auth_basic_user_file /home/trac/htpasswd;

              # socket address
              fastcgi_pass   unix:/home/trac/run/instance.sock;

              # python - wsgi specific
              fastcgi_param HTTPS on;

              ## WSGI REQUIRED VARIABLES
              # WSGI application name - trac instance prefix.
  	    # (Or ``fastcgi_param  SCRIPT_NAME  /some/prefix``.)
              fastcgi_param  SCRIPT_NAME        "";
              fastcgi_param  PATH_INFO          $path_info;

              ## WSGI NEEDED VARIABLES - trac warns about them
              fastcgi_param  REQUEST_METHOD     $request_method;
              fastcgi_param  SERVER_NAME        $server_name;
              fastcgi_param  SERVER_PORT        $server_port;
              fastcgi_param  SERVER_PROTOCOL    $server_protocol;

              # for authentication to work
              fastcgi_param  AUTH_USER          $remote_user;
              fastcgi_param  REMOTE_USER        $remote_user;
          }
      }
  }}}

  2) Modified trac.fcgi:

  {{{
  #!/usr/bin/env python
  import os
  sockaddr = '/home/trac/run/instance.sock'
  os.environ['TRAC_ENV'] = '/home/trac/instance'

  try:
       from trac.web.main import dispatch_request
       import trac.web._fcgi

       fcgiserv = trac.web._fcgi.WSGIServer(dispatch_request, 
            bindAddress = sockaddr, umask = 7)
       fcgiserv.run()

  except SystemExit:
      raise
  except Exception, e:
      print 'Content-Type: text/plain\r\n\r\n',
      print 'Oops...'
      print
      print 'Trac detected an internal error:'
      print
      print e
      print
      import traceback
      import StringIO
      tb = StringIO.StringIO()
      traceback.print_exc(file=tb)
      print tb.getvalue()

  }}}

  3) reload nginx and launch trac.fcgi like that:

  {{{
  trac@trac.example ~ $ ./trac-standalone-fcgi.py 
  }}}

  The above assumes that:
   * There is a user named 'trac' for running trac instances and keeping trac environments in its home directory.
   * /home/trac/instance contains a trac environment
   * /home/trac/htpasswd contains authentication information
   * /home/trac/run is owned by the same group the nginx runs under
    * and if your system is Linux the /home/trac/run has setgid bit set (chmod g+s run)
    * and patch from ticket #T7239 is applied, or you'll have to fix the socket file permissions every time

  Unfortunately nginx does not support variable expansion in fastcgi_pass directive. 
  Thus it is not possible to serve multiple trac instances from one server block. 

  If you worry enough about security, run trac instances under separate users. 

  Another way to run trac as a FCGI external application is offered in ticket #T6224

  ----
  See also:  TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracCgi CGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]


name: TracFineGrainedPermissions
author: trac
ipnr: 127.0.0.1
text:
  = Fine grained permissions =

  Before Trac 0.11, it was only possible to define fine-grained permissions checks on the repository browser sub-system.

  Since 0.11, there's a general mechanism in place that allows custom permission policy plugins to grant or deny any action on any kind of Trac resources, even at the level of specific versions of such resources.

  == Permission Policies ==

  === !AuthzPolicy ===

  An example policy based on an Authz-style system has been added. See
  [trac:source:branches/0.11-stable/sample-plugins/permissions/authz_policy.py authz_policy.py] for details (current version requires >= Python 2.4). (See also [trac:source:branches/0.11-stable/sample-plugins/permissions sample-plugins/permissions] for more samples.)

   - Install [http://www.voidspace.org.uk/python/configobj.html ConfigObj] (required).
   - Copy authz_policy.py into your plugins directory.
   - Put a [http://swapoff.org/files/authzpolicy.conf authzpolicy.conf] file somewhere (preferably on a secured location on the server, not readable for others than the webuser.
   - Update your `trac.ini`:
  {{{
  [trac]
  ...
  permission_policies = AuthzPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy

  [authz_policy]
  authz_file = /some/trac/env/conf/authzpolicy.conf

  [components]
  ...
  authz_policy = enabled
  }}}

  Note that the order in which permission policies are specified is quite critical, 
  as policies will be examined in the sequence provided.

  A policy will return either `True`, `False` or `None` for a given permission check.
  Only if the return value is `None` will the ''next'' permission policy be consulted.
  If no policy explicitly grants the permission, the final result will be `False` 
  (i.e. no permission).

  For example, if the `authz_file` contains:
  {{{
  [wiki:WikiStart@*]
  * = WIKI_VIEW

  [wiki:PrivatePage@*]
  john = WIKI_VIEW
  * =
  }}}
  and the default permissions are set like this:
  {{{
  john           WIKI_VIEW
  jack           WIKI_VIEW
  # anonymous has no WIKI_VIEW
  }}}

  Then: 
   - All versions of WikiStart will be viewable by everybody (including anonymous)
   - !PrivatePage will be viewable only by john
   - other pages will be viewable only by john and jack


  === mod_authz_svn-like permission policy ===

  At the time of this writing, the old fine grained permissions system from Trac 0.10 and before used for restricting access to the repository has not yet been converted to a permission policy component, but from the user point of view, this makes little if no difference.

  That kind of fine-grained permission control needs a definition file, which is the one used by Subversion's mod_authz_svn. 
  More information about this file format and about its usage in Subversion is available in the [http://svnbook.red-bean.com/svnbook/book.html#svn-ch-6-sect-4.4.2 Subversion Book (Per-Directory Access Control)].

  Example:
  {{{
  [/]
  * = r

  [/branches/calc/bug-142]
  harry = rw
  sally = r

  [/branches/calc/bug-142/secret]
  harry =
  }}}

   * '''/''' = ''Everyone has read access by default''
   * '''/branches/calc/bug-142''' = ''harry has read/write access, sally read only''
   * '''/branches/calc/bug-142/secret''' = ''harry has no access, sally has read access (inherited as a sub folder permission)''

  ==== Trac Configuration ====

  To activate fine grained permissions you __must__ specify the {{{authz_file}}} option in the {{{[trac]}}} section of trac.ini. If this option is set to null or not specified the permissions will not be used.

  {{{
  [trac]
  authz_file = /path/to/svnaccessfile
  }}}

  if you want to support the use of the `[`''modulename''`:/`''some''`/`''path''`]` syntax within the `authz_file`, add 

  {{{
  authz_module_name = modulename
  }}}

  where ''modulename'' refers to the same repository indicated by the `repository_dir` entry in the `[trac]` section.

  '''Note:''' Usernames inside the Authz file __must__ be the same as those used inside trac. 

  ==== Subversion Configuration ====

  The same access file is typically applied to the corresponding Subversion repository using an Apache directive like this:
  {{{
  <Location /repos>
    DAV svn
    SVNParentPath /usr/local/svn

    # our access control policy
    AuthzSVNAccessFile /path/to/svnaccessfile
  </Location>
  }}}

  For information about how to restrict access to entire projects in a multiple project environment see [trac:wiki:TracMultipleProjectsSVNAccess]

  == Getting TracFineGrainedPermissions to work ==

  Don't forget to restart Trac engine to apply new configuration if you are running tracd standalone server.

  ----
  See also: TracPermissions
  http://trac-hacks.org/wiki/FineGrainedPageAuthzEditorPlugin for a simple editor plugin.


name: TracGuide
author: trac
ipnr: 127.0.0.1
text:
  = 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://trac.edgewall.org Trac Project] itself.

  == Table of Contents ==
  Currently available documentation:
   * TracGuide (This page)  -- Documentation starting point.
   * '''Administrator Guide'''
     * TracInstall -- How to install and run Trac.
     * TracUpgrade -- How to upgrade existing installations.
     * TracAdmin -- Administering 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.
     * TracLogging -- The Trac logging facility.
     * TracNotification -- Email notification.
     * TracWorkflow -- Configurable Ticket Workflow.
   * '''User Guide'''
     * TracWiki -- How to use the built-in Wiki.
     * TracTimeline -- The timeline provides a historic perspective on a project.
     * TracRss -- RSS content syndication in Trac.
     * ''The Version Control Subsystem''
       * TracBrowser -- Browsing source code with Trac.
       * TracChangeset -- Viewing changes to source code.
       * TracRevisionLog -- Viewing change history.
     * ''The Ticket Subsystem''
       * TracTickets -- Using the issue tracker.
       * TracReports -- Writing and using reports.
       * TracQuery -- Executing custom ticket queries.
       * TracRoadmap -- The roadmap helps tracking project progress.
   * [trac: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://trac.edgewall.org/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.

  Finally, developer documentation can be found in [trac:TracDev TracDev] and its sub-pages.


name: TracImport
author: trac
ipnr: 127.0.0.1
text:
  = Importing ticket data =

  == Bugzilla ==

  Ticket data can be imported from Bugzilla using the [http://trac.edgewall.org/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://trac.edgewall.org/browser/trunk/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution.

  == Mantis ==

  NB! The mantis2trac script now lives at http://trac-hacks.org/wiki/MantisImportScript . You can always get the latest version from http://trac-hacks.org/changeset/latest/mantisimportscript?old_path=/&filename=mantisimportscript&format=zip

  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 (as long as the files live in the mantis db, not on the filesystem) 

  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.

  === Using a comma delimited file - CSV ===
  See [http://trac.edgewall.org/attachment/wiki/TracSynchronize/csv2trac.2.py] for details.  This approach is particularly useful if one needs to enter a large number of tickets by hand. (note that the ticket type type field, (task etc...) is also needed for this script to work with more recent Trac releases)


name: TracIni
author: trac
ipnr: 127.0.0.1
text:
  = The Trac Configuration File =
  [[TracGuideToc]]

  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.

  == Global Configuration ==

  In versions prior to 0.11, the global configuration was by default located in `$prefix/share/trac/conf/trac.ini` or sometimes /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 = /usr/share/trac/conf/trac.ini
  }}}

  Note that you can also specify a global option file when creating a new project,  by adding the option
  `--inherit=/path/to/global/options` to [TracAdmin trac-admin]'s `initenv` command.
  If you would not do this but nevertheless intend to use a global option file with your new environment, 
  you would have to go through the newly generated conf/trac.ini file and delete the entries that would
  otherwise override those set in the global file.


  == Reference ==

  This is a brief reference of available configuration options.

  [[TracIni()]]


  == [components] == #components-section
  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 [wiki:TracReports 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.

  See the ''Plugins'' page on ''About Trac'' to get the list of active components (requires `CONFIG_VIEW` [wiki:TracPermissions permissions].)

  See also: TracPlugins

  == [ticket-custom] == #ticket-custom-section

  In this section, you can define additional fields for tickets. See TracTicketsCustomFields for more details.

  == [ticket-workflow] == #ticket-workflow-section
  ''(since 0.11)''

  The workflow for tickets is controlled by plugins. 
  By default, there's only a `ConfigurableTicketWorkflow` component in charge. 
  That component allows the workflow to be configured via this section in the trac.ini file.
  See TracWorkflow for more details.

  == [milestone-groups] == #milestone-groups-section
  ''(since 0.11)''

  As the workflow for tickets is now configurable, there can be many ticket states,
  and simply displaying closed tickets vs. all the others is maybe not appropriate 
  in all cases. This section enables one to easily create ''groups'' of states 
  that will be shown in different colors in the milestone progress bar.

  Example configuration (the default only has closed and active):
  {{{
  closed = closed
  closed.order = 0                     # sequence number in the progress bar
  closed.query_args = group=resolution # optional extra param for the query
  closed.overall_completion = true     # indicates groups that count for overall completion percentage

  new = new
  new.order = 1
  new.css_class = new
  new.label = new

  active = *                           # one catch-all group is allowed
  active.order = 1
  active.css_class = open              # CSS class for this interval
  active.label = in progress           # Displayed label for this group
  }}}

  The definition consists in a comma-separated list of accepted status.
  Also, '*' means any status and could be used to associate all remaining
  states to one catch-all group.

  The CSS class can be one of: new (yellow), open (no color) or
  closed (green). New styles can easily be added using the following
  selector:  `table.progress td.<class>`

  == [svn:externals] == #svn:externals-section
  ''(since 0.11)''

  The TracBrowser for Subversion can interpret the `svn:externals` property of folders out of the box.
  However, if those externals are ''not'' using the `http:` protocol, or if a link to a different repository browser (such another Trac or [http://www.viewvc.org/ ViewVC]) is desired, then Trac needs to be able to map an external prefix to this other URL.

  This mapping is done in the `[svn:externals]` section of the TracIni

  Example:
  {{{
  [svn:externals]
  1 = svn://server/repos1 http://trac/proj1/browser/$path?rev=$rev
  2 = svn://server/repos2 http://trac/proj2/browser/$path?rev=$rev
  3 = http://theirserver.org/svn/eng-soft       http://ourserver/viewvc/svn/$path/?pathrev=25914
  4 = svn://anotherserver.com/tools_repository  http://ourserver/trac/support/browser/$path?rev=$rev
  }}}
  With the above, the `svn://anotherserver.com/tools_repository/tags/1.1/tools` external will be mapped to `http://ourserver/trac/support/browser/tags/1.1/tools?rev=` (and `rev` will be set to the appropriate revision number if the external additionally specifies a revision, see the [http://svnbook.red-bean.com/en/1.4/svn.advanced.externals.html SVN Book on externals] for more details).

  Note that the number used as a key in the above section is purely used as a place holder, as the URLs themselves can't be used as a key due to various limitations in the configuration file parser.

  ----
  See also: TracGuide, TracAdmin, TracEnvironment


name: TracInstall
author: trac
ipnr: 127.0.0.1
text:
  = Trac Installation Guide for 0.11 = 
  [[TracGuideToc]]

  Trac is written in the Python programming language and needs a database, [http://sqlite.org/ SQLite], [http://www.postgresql.org/ PostgreSQL], or [http://mysql.com/ MySQL]. For HTML rendering, Trac uses the [http://genshi.edgewall.org Genshi] templating system.

  What follows are generic instructions for installing and setting up Trac and its requirements. While you can find instructions for installing Trac on specific systems at TracInstallPlatforms on the main Trac site, please be sure to '''first read through these general instructions''' to get a good understanding of the tasks involved.

  == Short - Install a released version ==
  For the quick install, make sure you have [http://python.org Python-2.5], [http://peak.telecommunity.com/DevCenter/EasyInstall#installing-easy-install easy_install] and SQlite-3.3.4 installed (or above). (You also might want to install python-dev to build genshi)
  {{{
  sudo easy_install Trac
  }}}

  == Requirements ==
  The hardware requirements for running Trac obviously depend on the expected data volume (number of wiki pages, tickets, revisions) and traffic. Very small projects will run fine with a 500MHz processor and 128MB RAM using SQLite. In general, the more RAM, the better. A fast hard disk also helps.

  To install Trac, the following software packages must be installed:

   * [http://www.python.org/ Python], version >= 2.3
     * if using mod_python together with xml-related things, use python-2.5. expat is namespaced there and does not cause apache to crash any more(see [http://www.dscpl.com.au/wiki/ModPython/Articles/ExpatCausingApacheCrash here] for details).
     * For RPM-based systems you might also need the `python-devel` and `python-xml` packages.
     * See instructions in ["TracOnWindows/Python2.5"]
   * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.6
   * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.5 (was version >= 0.4.1 on previous 0.11 release candidates)
   * You also need a database system and the corresponding python drivers for it.
     The database can be either SQLite, PostgreSQL or ''MySQL (experimental)''.
   * Optional if some plugins require it: [http://www.clearsilver.net/ ClearSilver]

  ==== For SQLite ====

   * [http://www.sqlite.org/ SQLite], version 3.3.4 and above preferred (note: it is preinstalled in Python 2.5.2).
   * If not using Python-2.5: [http://pysqlite.org/ PySQLite], version 1.x (for SQLite 2.x) or version 2.x (for SQLite 3.x), version 2.3.2 preferred. For details see [trac:PySqlite PySqlite]

  ''Note: It appears that PySQLite 2.x is required for Trac 0.9+/SQLite 3.x if you plan to use the 'trac-post-commit-hook.py' script available from the 'contrib' section of the source repository.''

  ''Note: Users of Mac OS X please take care; the Apple-supplied SQLite contains additional code to support file locking on network filesystems like AFP or SMB. This is not presently (3.3.6) in the mainline sources, so if you build your own SQLite from source it will not function correctly on such filesystems - typically it gives the error "{{{database is locked}}}". [http://www.alastairs-place.net/2006/07/sqlite_and_mac/ A patch] is available for version 3.3.6, based on Apple's code, otherwise you're probably best off using the Apple supplied version (presently 3.1.3).''

  ==== For PostgreSQL ====

   * [http://www.postgresql.org/ PostgreSQL]
   * [http://initd.org/projects/psycopg2 psycopg2]
   * See [trac:wiki:DatabaseBackend#Postgresql DatabaseBackend]

  '''Warning''': PostgreSQL 8.3 uses a strict type checking mechanism. To use Trac with the 8.3 Version of PostgreSQL, you will need [http://trac.edgewall.org/changeset/6512 trac-0.11] or later.

  ==== For MySQL ====

  '''Warning''': MySQL support is currently ''still'' experimental. That means it works for some people, but several issues remain, in particular regarding the use of unicode and the key length in the repository cache. See [trac:MySqlDb MySqlDb] for more detailed information.

   * [http://mysql.com/ MySQL], version 4.1 or later
   * [http://sf.net/projects/mysql-python MySQLdb], version 1.2.1 or later

  == Optional Requirements ==

  ==== Version Control System ====

  '''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently not supported.

   * [http://subversion.tigris.org/ Subversion], version >= 1.0. (versions recommended: 1.2.4, 1.3.2 or 1.4.2) and the '''''corresponding''''' Python bindings. For troubleshooting, check [trac:TracSubversion TracSubversion]
     * Trac uses the [http://svnbook.red-bean.com/svnbook-1.1/ch08s02.html#svn-ch-8-sect-2.3 SWIG] bindings included in the Subversion distribution, '''not''' [http://pysvn.tigris.org/ PySVN] (which is sometimes confused with the standard SWIG bindings).
     * If Subversion was already installed without the SWIG bindings, on Unix you'll need to re-`configure` Subversion and `make swig-py`, `make install-swig-py`.
     * There are [http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91 pre-compiled bindings] available for win32. 
   * Support for other version control systems is provided via third-parties. See [trac:PluginList PluginList] and [trac:VersioningSystemBackend VersioningSystemBackend].

  ==== Web Server ====
   * A CGI-capable web server (see TracCgi), or
   * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi), or
   * an [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp]), or
   * [http://httpd.apache.org/ Apache] with [http://code.google.com/p/modwsgi/ mod_wsgi] (see [wiki:TracModWSGI] or http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac)
      * This should work with Apache 1.3, 2.0 or 2.2 and promises to deliver more performance than using mod_python. A little less mature than mod_python.
   * [http://httpd.apache.org/ Apache] with [http://www.modpython.org/ mod_python 3.1.3+] (see TracModPython)
      * When installing mod_python the development versions of Python and Apache are required (actually the libraries and header files)

  For those stuck with Apache 1.3, it is also possible to get Trac working with [http://www.modpython.org/ mod_python 2.7] (see [wiki:TracModPython2.7 TracModPython2.7]). This guide hasn't been updated since 0.84, so it may or may not work.

  ==== Other Python Utilities ====
   * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9 for WikiRestructuredText.
   * [http://pygments.pocoo.org Pygments] for '''syntax highlighting''', although [http://silvercity.sourceforge.net/ SilverCity] >= 0.9.7 and/or [http://gnu.org/software/enscript/enscript.html GNU Enscript] are also possible. Refer to TracSyntaxColoring for details.
   * [http://pytz.sf.net pytz] to get a complete list of time zones, otherwise Trac will fall back on a shorter list from an internal time zone implementation.

  '''Attention''': The various available versions of these dependencies are not necessarily interchangable, so please pay attention to the version numbers above. If you are having trouble getting Trac to work please double-check all the dependencies before asking for help on the [trac:MailingList MailingList] or [trac:IrcChannel IrcChannel].

  Please refer to the documentation of these packages to find out how they are best installed. In addition, most of the [trac:TracInstallPlatforms platform-specific instructions] also describe the installation of the dependencies. Keep in mind however that the information there ''probably concern older versions of Trac than the one you're installing'' (there are even some pages that are still talking about Trac 0.8!).

  == Installing Trac ==

  One way to install Trac is using `setuptools`.
  With setuptools you can install Trac from the subversion repository; for example,
  to install release version 0.11 do:
  {{{
  easy_install http://svn.edgewall.org/repos/trac/tags/trac-0.11
  }}}

  But of course the python-typical setup at the top of the source directory also works:
  {{{
  $ python ./setup.py install
  }}}

  ''Note: you'll need root permissions or equivalent for this step.''

  This will byte-compile the python source code and install it as an .egg file or folder in the `site-packages` directory
  of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as htdocs and templates.

  The script will also install the [wiki:TracAdmin trac-admin] command-line tool, used to create and maintain [wiki:TracEnvironment project environments], as well as the [wiki:TracStandalone tracd] standalone server.

  ==== Advanced Options ====

  To install Trac to a custom location, or find out about other advanced installation options, run:
  {{{
  easy_install --help
  }}}

  Also see [http://docs.python.org/inst/inst.html Installing Python Modules] for detailed information.

  Specifically, you might be interested in:
  {{{
  easy_install --prefix=/path/to/installdir
  }}}
  or, if installing Trac to a Mac OS X system:
  {{{
  easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages
  }}}

  The above will place your `tracd` and `trac-admin` commands into `/usr/local/bin` and will install the Trac libraries and dependencies into `/Library/Python/2.5/site-packages`, which is Apple's preferred location for third-party Python application installations.

  == Creating a Project Environment ==

  A [wiki:TracEnvironment Trac environment] is the backend storage where Trac stores information like wiki pages, tickets, reports, settings, etc. An environment is basically a directory that contains a human-readable configuration file and various other files and directories.

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

  [wiki:TracAdmin trac-admin] will prompt you for the information it needs to create the environment, such as the name of the project, the type and the path to an existing [wiki:TracEnvironment#SourceCodeRepository source code repository], the [wiki:TracEnvironment#DatabaseConnectionStrings database connection string], and so on. If you're not sure what to specify for one of these options, just leave it blank to use the default value. The database connection string in particular will always work as long as you have SQLite installed. Leaving the path to the source code repository empty will disable any functionality related to version control, but you can always add that back when the basic system is running.

  Also note that the values you specify here can be changed later by directly editing the [wiki:TracIni] configuration file.

  ''Note: The user account under which the web server runs will require write permissions to the environment directory and all the files inside.  On Linux, with the web server running as user apache and group apache, enter:''

    chown -R apache.apache /path/to/myproject

  '''Warning: If the trac.cgi files are not installed where you expect, then the current documentation is insufficient; it might be necessary to use the 'deploy' command in trac-admin.  See tickets http://trac.edgewall.org/ticket/7312 and possibly http://trac.edgewall.org/ticket/6827'''

  == Running the Standalone Server ==

  After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]:
  {{{
  $ tracd --port 8000 /path/to/myproject
  }}}

  Then, fire up a browser and visit `http://localhost:8000/`. You should get a simple listing of all environments that tracd knows about. Follow the link to the environment you just created, and you should see Trac in action. If you only plan on managing a single project with trac you can have the standalone server skip the environment list by starting it like this:
  {{{
  $ tracd -s --port 8000 /path/to/myproject
  }}}


  == Running Trac on a Web Server ==

  Trac provides three options for connecting to a "real" web server: [wiki:TracCgi CGI], [wiki:TracFastCgi FastCGI] and [wiki:TracModPython mod_python]. For decent performance, it is recommended that you use either FastCGI or mod_python.

  If you're not afraid of running newer code, you can also try running Trac on [wiki:TracModWSGI mod_wsgi]. This should deliver even better performance than mod_python, but the module isn't as extensively tested as mod_python.

  Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS.

  ==== Setting up the Plugin Cache ====

  Some Python plugins need to be extracted to a cache directory. By default the cache resides in the home directory of the current user. When running Trac on a Web Server as a dedicated user (which is highly recommended) who has no home directory, this might prevent the plugins from starting. To override the cache location you can set the PYTHON_EGG_CACHE environment variable. Refer to your server documentation for detailed instructions.

  == Configuring Authentication ==

  The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac. The basic procedure is described in the [wiki:TracCgi#AddingAuthentication "Adding Authentication"] section on the TracCgi page. To learn how to setup authentication for the frontend you're using, please refer to one of the following pages:

   * TracStandalone if you use the standalone server, `tracd`.
   * TracCgi if you use the CGI or FastCGI methods.
   * TracModPython if you use the mod_python method.

  == Automatic reference to the SVN changesets in Trac tickets ==

  You can configure SVN to automatically add a reference to the changeset into the ticket comments, whenever files are committed to the repository. The description of the commit needs to contain one of the following formulas:
   * '''Refs #123''' - to reference this changeset in #123 ticket
   * '''Fixes #123''' - to reference this changeset and close #123 ticket with the default status ''fixed''

  All you have to do is to edit the ''post-commit'' hook in your SVN repository and make it execute ''trac-post-commit-hook'' coming with Trac.

  If you are editing the ''post-commit'' hook for the first time you need to navigate to your SVN repository's hooks subfolder and rename existing there ''post-commit'' template:

  {{{
  $ cd /path/to/svn/repository/hooks
  $ mv post-commit.tmpl post-commit
  $ chmod 755 post-commit
  }}}

  Next open it in any text editor and add a line with path to the Trac environment connected with this SVN repository and another line executing the ''trac-post-commit-hook'' script:

  {{{
  REPOS="$1"
  REV="$2"
  TRAC_ENV="/path/to/your/trac/project"

  /usr/bin/python /usr/local/bin/trac-post-commit-hook -p "$TRAC_ENV" -r "$REV"
  }}}

  Make sure that ''trac-post-commit-hook'' exists in above path with execution permissions for the same user which SVN is running from. This script can be found in contrib subfolder of your Trac distribution and the latest version can be always downloaded from [source:trunk/contrib/trac-post-commit-hook].


  == Platform-specifics installations ==

   * See [trac:TracInstallPlatforms TracInstallPlatforms]
   

  == Using Trac ==

  Once you have your Trac site up and running, you should be able to browse your subversion repository, create tickets, view the timeline, etc.

  Keep in mind that anonymous (not logged in) users can by default access most but not all of the features. You will need to configure authentication and grant additional [wiki:TracPermissions permissions] to authenticated users to see the full set of features.

  '' Enjoy! ''

  [trac:TracTeam The Trac Team]

  ----
  See also:  TracInstallPlatforms, TracGuide, TracCgi, TracFastCgi, TracModPython, [wiki:TracModWSGI], TracUpgrade, TracPermissions


name: TracInterfaceCustomization
author: trac
ipnr: 127.0.0.1
text:
  = Customizing the Trac Interface =
  [[TracGuideToc]]

  == Introduction ==
  This page is meant to give users suggestions on how they can customize the look of Trac.  Topics on this page cover editing the HTML templates and CSS files, but not the program code itself.  The topics are intended to show users how they can modify the look of Trac to meet their specific needs.  Suggestions for changes to Trac's interface applicable to all users should be filed as tickets, not listed on this page.

  == Project Logo and Icon ==
  The easiest parts of the Trac interface to customize are the logo and the site icon.  Both of these can be configured with settings in [wiki:TracIni trac.ini].

  The logo or icon image should be put in a folder named "htdocs" in your project's environment folder.  (''Note: in projects created with a Trac version prior to 0.9 you will need to create this folder'')

   ''Note: you can actually put the logo and icon anywhere on your server (as long as it's accessible through the web server), and use their absolute or server-relative URLs in the configuration.''

  Now configure the appropriate section of your [wiki:TracIni trac.ini]:

  === Logo ===
  Change the `src` setting to `site/` followed by the name of your image file.  The `width` and `height` settings should be modified to match your image's dimensions (the Trac chrome handler uses "`site/`" for files within the project directory `htdocs` and "`common/`" for the common ones).

  {{{
  [header_logo]
  src = site/my_logo.gif
  alt = My Project
  width = 300
  height = 100
  }}}

  === Icon ===
  Icons should be a 16x16 image in `.gif` or `.ico` format.  Change the `icon` setting to `site/` followed by the name of your icon file.  Icons will typically be displayed by your web browser next to the site's URL and in the `Bookmarks` menu.

  {{{
  [project]
  icon = site/my_icon.ico
  }}}

  Note though that this icon is ignored by Internet Explorer, which only accepts a file named ``favicon.ico`` at the root of the host. To make the project icon work in both IE and other browsers, you can store the icon in the document root of the host, and reference it from ``trac.ini`` as follows:

  {{{
  [project]
  icon = /favicon.ico
  }}}

  == Custom Navigation Entries ==
  The new [mainnav] and [metanav] can now be used to customize the text and link used for the navigation items, or even to disable them (but not for adding new ones).

  In the following example, we rename the link to the Wiki start "Home", and hide the "Help/Guide". We also make the "View Tickets" entry link to a specific report .
  {{{
  [mainnav]
  wiki.label = Home
  tickets.href = /report/24

  [metanav]
  help = disabled
  }}}

  See also TracNavigation for a more detailed explanation of the mainnav and metanav terms.

  == Site Appearance == #SiteAppearance

  Trac is using [http://genshi.edgewall.org Genshi] as the templating engine. Documentation is yet to be written, in the meantime the following tip should work.

  Say you want to add a link to a custom stylesheet, and then your own
  header and footer. Save the following content as 'site.html' inside your projects templates directory (each Trac project can have their own site.html), e.g. {{{/path/to/env/templates/site.html}}}:

  {{{
  #!xml
  <html xmlns="http://www.w3.org/1999/xhtml"
        xmlns:py="http://genshi.edgewall.org/"
        py:strip="">

    <!--! Add site-specific style sheet -->
    <head py:match="head" py:attrs="select('@*')">
      ${select('*|comment()|text()')}
      <link rel="stylesheet" type="text/css"
            href="${href.chrome('site/style.css')}" />
    </head>

    <body py:match="body" py:attrs="select('@*')">
      <!--! Add site-specific header -->
      <div id="siteheader">
        <!--! Place your header content here... -->
      </div>

      ${select('*|text()')}

      <!--! Add site-specific footer -->
      <div id="sitefooter">
        <!--! Place your footer content here... -->
      </div>
    </body>
  </html>
  }}}

  Those who are familiar with XSLT may notice that Genshi templates bear some similarities. However, there are some Trac specific features - for example '''${href.chrome('site/style.css')}''' attribute references template placed into environment's ''htdocs/''  In a similar fashion '''${chrome.htdocs_location}''' is used to specify common ''htdocs/'' directory from Trac installation.

  site.html is one file to contain all your modifications. It usually works by the py:match (element of attribute), and it allows you to modify the page as it renders - the matches hook onto specific sections depending on what it tries to find
  and modify them. A site.html can contain any number of such py:match sections for whatever you need to modify. This is all [http://genshi.edgewall.org/ Genshi], so the docs on the exact syntax can be found there. 


  Example snippet of adding introduction text to the new ticket form (hide when preview):

  {{{
  #!xml
  <form py:match="div[@id='content' and @class='ticket']/form" py:attrs="select('@*')">
    <py:if test="req.environ['PATH_INFO'] == '/newticket' and (not 'preview' in req.args)">
      <p>Please make sure to search for existing tickets before reporting a new one!</p>
    </py:if>
    ${select('*')} 
  </form>
  }}}

  This example illustrates a technique of using '''`req.environ['PATH_INFO']`''' to limit scope of changes to one view only. For instance, to make changes in site.html only for timeline and avoid modifying other sections - use  ''`req.environ['PATH_INFO'] == '/timeline'`'' condition in <py:if> test.

  If the environment is upgraded from 0.10 and a `site_newticket.cs` file already exists, it can actually be loaded by using a workaround - providing it contains no ClearSilver processing. In addition, as only one element can be imported, the content needs some sort of wrapper such as a `<div>` block or other similar parent container. The XInclude namespace must be specified to allow includes, but that can be moved to document root along with the others:
  {{{
  #!xml
  <form py:match="div[@id='content' and @class='ticket']/form" py:attrs="select('@*')"
          xmlns:xi="http://www.w3.org/2001/XInclude">
    <py:if test="req.environ['PATH_INFO'] == '/newticket' and (not 'preview' in req.args)"> 
      <xi:include href="site_newticket.cs"><xi:fallback /></xi:include>
    </py:if>
    ${select('*')} 
  </form>
  }}}

  Also note that the `site.html` (despite its name) can be put in a common templates directory - see the `[inherit] templates_dir` option. This could provide easier maintainence (and a migration path from 0.10 for larger installations) as one new global `site.html` file can be made to include any existing header, footer and newticket snippets.

  == Project List == #ProjectList

  You can use a custom Genshi template to display the list of projects if you are using Trac with multiple projects.  

  The following is the basic template used by Trac to display a list of links to the projects.  For projects that could not be loaded it displays an error message. You can use this as a starting point for your own index template.

  {{{
  #!text/html
  <!DOCTYPE html
      PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
      "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
  <html xmlns="http://www.w3.org/1999/xhtml"
        xmlns:py="http://genshi.edgewall.org/"
        xmlns:xi="http://www.w3.org/2001/XInclude">
    <head>
      <title>Available Projects</title>
    </head>
    <body>
      <h1>Available Projects</h1>
      <ul>
        <li py:for="project in projects" py:choose="">
          <a py:when="project.href" href="$project.href"
             title="$project.description">$project.name</a>
          <py:otherwise>
            <small>$project.name: <em>Error</em> <br /> ($project.description)</small>
          </py:otherwise>
        </li>
      </ul>
    </body>
  </html>
  }}}

  Once you've created your custom template you will need to configure the webserver to tell Trac where the template is located (pls verify ... not yet changed to 0.11):

  For [wiki:TracFastCgi FastCGI]:
  {{{
  FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects \
                -initial-env TRAC_ENV_INDEX_TEMPLATE=/path/to/template
  }}}

  For [wiki:TracModPython mod_python]:
  {{{
  PythonOption TracEnvParentDir /parent/dir/of/projects
  PythonOption TracEnvIndexTemplate /path/to/template
  }}}

  For [wiki:TracCgi CGI]:
  {{{
  SetEnv TRAC_ENV_INDEX_TEMPLATE /path/to/template
  }}}

  For [wiki:TracStandalone], you'll need to set up the `TRAC_ENV_INDEX_TEMPLATE` environment variable in the shell used to launch tracd:
   - Unix
     {{{
  #!sh
  $ export TRAC_ENV_INDEX_TEMPLATE=/path/to/template
     }}}
   - Windows
     {{{
  #!sh
  $ set TRAC_ENV_INDEX_TEMPLATE=/path/to/template
     }}}

  == Project Templates ==

  The appearance of each individual Trac environment (that is, instance of a project) can be customized independently of other projects, even those hosted by the same server. The recommended way is to use a `site.html` template (see [#SiteAppearance]) whenever possible. Using `site.html` means changes are made to the original templates as they are rendered, and you should not normally need to redo modifications whenever Trac is upgraded. If you do make a copy of `theme.html` or any other Trac template, you need to migrate your modifiations to the newer version - if not, new Trac features or bug fixes may not work as expected.

  With that word of caution, any Trac template may be copied and customized. The default Trac templates are located inside the installed Trac egg (`/usr/lib/pythonVERSION/site-packages/Trac-VERSION.egg/trac/templates, .../trac/ticket/templates, .../trac/wiki/templates, ++`). The [#ProjectList] template file is called `index.html`, while the template responsible for main layout is called `theme.html`. Page assets such as images and CSS style sheets are located in the egg's `trac/htdocs` directory.

  However, do not edit templates or site resources inside the Trac egg - installing Trac again can completely delete your modifications. Instead use one of two alternatives:
   * For a modification to one project only, copy the template to project `templates` directory.
   * For a modification shared by several projects, copy the template to a shared location and have each project point to this location using the `[inherit] templates_dir =` trac.ini option.

  Trac resolves requests for a template by first looking inside the project, then in any inherited templates location, and finally inside the Trac egg.

  Trac caches templates in memory by default to improve performance. To apply a template you need to restart the server.
  ----
  See also TracGuide, TracIni


name: TracLinks
author: trac
ipnr: 127.0.0.1
text:
  = Trac Links =
  [[TracGuideToc]]

  TracLinks are a fundamental feature of Trac, because they allow easy hyperlinking between the various entities in the system—such as tickets, reports, changesets, Wiki pages, milestones, and source files—from anywhere WikiFormatting is used.

  TracLinks are generally of the form '''type:id''' (where ''id'' represents the
  number, name or path of the item) though some frequently used kinds of items
  also have short-hand notations.

  == Where to use TracLinks ==
  You can use TracLinks in:

   * Source code (Subversion) commit messages
   * Wiki pages
   * Full descriptions for tickets, reports and milestones

  and any other text fields explicitly marked as supporting WikiFormatting.

  Some examples:
   * Tickets: '''!#1''' or '''!ticket:1'''
   * Ticket comments: '''!comment:1:ticket:2''' 
   * Reports: '''!{1}''' or '''!report:1'''
   * Changesets: '''!r1''', '''![1]''', '''!changeset:1''' or (restricted) '''![1/trunk]''', '''!changeset:1/trunk'''
   * Revision log: '''!r1:3''', '''![1:3]''' or '''!log:@1:3''', '''!log:trunk@1:3''', '''![2:5/trunk]'''
   * Diffs (requires [trac:milestone:0.10 0.10]): '''!diff:@1:3''', '''!diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default''' or '''!diff:trunk/trac@3538//sandbox/vc-refactoring@3539'''
   * Wiki pages: '''!CamelCase''' or '''!wiki:CamelCase'''
   * Parent page: '''![..]'''
   * Milestones: '''!milestone:1.0'''
   * Attachment: '''!attachment:example.tgz''' (for current page attachment), '''!attachment:attachment.1073.diff:ticket:944''' 
  (absolute path)
   * Files: '''!source:trunk/COPYING'''
   * A specific file revision: '''!source:/trunk/COPYING@200'''
   * A particular line of a specific file revision: '''!source:/trunk/COPYING@200#L25'''
  Display:
   * Tickets: #1 or ticket:1
   * Ticket comments: comment:1:ticket:2 
   * Reports: {1} or report:1
   * Changesets: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk
   * Revision log: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
   * Diffs (requires [milestone:0.10 0.10]): diff:@1:3, diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default or diff:trunk/trac@3538//sandbox/vc-refactoring@3539
   * Wiki pages: CamelCase or wiki:CamelCase
   * Parent page: [..]
   * Milestones: milestone:1.0
   * Attachment: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944 
  (absolute path)
   * Files: source:trunk/COPYING
   * A specific file revision: source:/trunk/COPYING@200
   * A particular line of a specific file revision: source:/trunk/COPYING@200#L25

  '''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to
  pages whose names do not follow WikiPageNames rules, i.e., single words,
  non-alphabetic characters, etc. See WikiPageNames for more about features specific
  to links to Wiki page names.

  Trac links using the full (non-shorthand) notation can also be given a custom
  link title like this:

  {{{
  [ticket:1 This is a link to ticket number one].
  }}}

  Display: [ticket:1 This is a link to ticket number one].

  If the title is omitted, only the id (the part after the colon) is displayed:

  {{{
  [ticket:1]
  }}}

  Display: [ticket:1]

  `wiki` is the default if the namespace part of a full link is omitted (''since version 0.10''):

  {{{
  [SandBox the sandbox]
  }}}

  Display: [SandBox the sandbox]

  TracLinks are a very simple idea, but actually allow quite a complex network of information. In practice, it's very intuitive and simple to use, and we've found the "link trail" extremely helpful to better understand what's happening in a project or why a particular change was made.


  == Advanced use of TracLinks ==

  === Relative links ===

  To create a link to a specific anchor in a page, use '#':
  {{{
   [#Relativelinks relative links]
  }}}
  Displays:
    [#Relativelinks relative links]

  Hint: when you move your mouse over the title of a section, a '¶' character will be displayed. This is a link to that specific section and you can use this to copy the `#...` part inside a relative link to an anchor.

  To create a link to a [trac:SubWiki SubWiki]-page just use a '/':
  {{{
   WikiPage/SubWikiPage or ./SubWikiPage
  }}}

  To link from a [trac:SubWiki SubWiki] page to a parent, simply use a '..':
  {{{
    [..]
  }}}

  To link from a [trac:SubWiki SubWiki] page to a sibling page, use a '../':
  {{{
    [../Sibling see next sibling]
  }}}

  ''(Changed in 0.11)'' Note that in Trac 0.10, using e.g. `[../newticket]`  may have worked for linking to the /newticket top-level URL, but now in 0.11 it will stay in the wiki namespace and link to a sibling page. See [#Server-relativelinks] for the new syntax.

  === InterWiki links ===

  Other prefixes can be defined freely and made to point to resources in other Web applications. The definition of those prefixes as well as the URLs of the corresponding Web applications is defined in a special Wiki page, the InterMapTxt page. Note that while this could be used to create links to other Trac environments, there's a more specialized way to register other Trac environments which offers greater flexibility.

  === InterTrac links ===

  This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.

  Any type of Trac links could be written in one Trac environment and actually refer to resources present in another Trac environment, provided the Trac link is prefixed by the name of that other Trac environment followed by a colon. That other Trac environment must be registered, under its name or an alias. See InterTrac for details. 

  A distinctive advantage of InterTrac links over InterWiki links is that the shorthand form of Trac links usually have a way to understand the InterTrac prefixes. For example, links to Trac tickets can be written #T234 (if T was set as an alias for Trac), links to Trac changesets can be written [trac 1508].

  === Server-relative links ===

  It is often useful to be able to link to objects in your project that
  have no built-in Trac linking mechanism, such as static resources, `newticket`,
  a shared `/register` page on the server, etc.

  To link to resources inside the project, use either an absolute path from the project root, 
  or a relative link from the URL of the current page (''Changed in 0.11''):

  {{{
  [/newticket Create a new ticket]
  [/ home]
  }}}

  Display: [/newticket newticket] [/ home]

  To link to another location on the server (outside the project), use the '//location' link syntax (''Changed in 0.11''):

  {{{
  [//register Register Here]
  }}}

  Display: [//register Register Here]

  === Quoting space in TracLinks ===

  Immediately after a TracLinks prefix, targets containing space characters should
  be enclosed in a pair of quotes or double quotes.
  Examples:
   * !wiki:"The whitespace convention"
   * !attachment:'the file.txt' or
   * !attachment:"the file.txt" 
   * !attachment:"the file.txt:ticket:123" 

  === Escaping Links ===

  To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
  {{{
   !NoLinkHere.
   ![42] is not a link either.
  }}}

  Display:
   !NoLinkHere.
   ![42] is not a link either.


  === Parameterized Trac links ===

  The Trac links target Trac resources which have generally more than one way to be rendered, according to some extra parameters. For example, a Wiki page can accept a `version` or a `format` parameter, a report can make use of dynamic variables, etc.

  Any Trac links can support an arbitrary set of parameters, written in the same way as they would be for the corresponding URL. Some examples:
   - `wiki:WikiStart?format=txt`
   - `ticket:1?version=1`
   - `[/newticket?component=module1 create a ticket for module1]`


  == TracLinks Reference ==
  The following sections describe the individual link types in detail, as well as several notes advanced usage of links.

  === attachment: links ===

  The link syntax for attachments is as follows:
   * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object
   * !attachment:the_file.txt:wiki:MyPage creates a link to the attachment the_file.txt of the !MyPage wiki page
   * !attachment:the_file.txt:ticket:753 creates a link to the attachment the_file.txt of the ticket 753

  Note that the older way, putting the filename at the end, is still supported: !attachment:ticket:753:the_file.txt.

  If you'd like to create a direct link to the content of the attached file instead of a link to the attachment page, simply use `raw-attachment:` instead of `attachment:`.

  This can be useful for pointing directly to an HTML document, for example. Note that for this use case, you'd have to allow the web browser to render the content by setting `[attachment] render_unsafe_content = yes` (see TracIni#attachment-section). Caveat: only do that in environments for which you're 100% confident you can trust the people who are able to attach files, as otherwise this would open up your site to [wikipedia:Cross-site_scripting cross-site scripting] attacks.

  See also [#export:links].

  === comment: links ===

  When you're inside a given tickets, you can simply write e.g. !comment:3 to link to the third change comment.
  It's also possible to link to a comment of a specific ticket from anywhere using one of the following syntax:
   - !comment:3:ticket:123 
   - !ticket:123#comment:3 (note that you can't write !#123#!comment:3!)

  === query: links ===

  See TracQuery#UsingTracLinks and [#ticket:links].

  === search: links ===

  See TracSearch#SearchLinks 

  === ticket: links ===

  Besides the obvious `ticket:id` form, it is also possible to specify a list of tickets or even a range of tickets instead of the `id`. This generates a link to a custom query view containing this fixed set of tickets.

  Example: 
   - `ticket:5000-6000`
   - `ticket:1,150`

  ''(since Trac 0.11)''

  === timeline: links ===

  Links to the timeline can be created by specifying a date in the ISO:8601 format. The date can be optionally followed by a time specification. The time is interpreted as being UTC time, but alternatively you can specify your local time, followed by your timezone if you don't want to compute the UTC time.

  Examples:
   - `timeline:2008-01-29`
   - `timeline:2008-01-29T15:48`
   - `timeline:2008-01-29T16:48Z+01`

  ''(since Trac 0.11)''

  === wiki: links ===

  See WikiPageNames and [#QuotingspaceinTracLinks quoting space in TracLinks] above.

  === Version Control related links ===
  ==== source: links ====

  The default behavior for a source:/some/path link is to open the directory browser 
  if the path points to a directory and otherwise open the log view.

  It's also possible to link directly to a specific revision of a file like this:
   - `source:/some/file@123` - link to the file's revision 123
   - `source:/some/file@head` - link explicitly to the latest revision of the file

  If the revision is specified, one can even link to a specific line number:
   - `source:/some/file@123#L10`
   - `source:/tag/0.10@head#L10`

  Finally, one can also highlight an arbitrary set of lines:
   - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103.
  ''(since 0.11)''

  ==== export: links ====

  To force the download of a file in the repository, as opposed to displaying it in the browser, use the `export` link.  Several forms are available:
   * `export:/some/file` - get the HEAD revision of the specified file
   * `export:123:/some/file` - get revision 123 of the specified file
   * `export:/some/file@123` - get revision 123 of the specified file

  This can be very useful for displaying XML or HTML documentation with correct stylesheets and images, in case that has been checked in into the repository. Note that for this use case, you'd have to allow the web browser to render the content by setting `[browser] render_unsafe_content = yes` (see TracIni#browser-section), otherwise Trac will force the files to be downloaded as attachments for security concerns. 

  If the path is to a directory in the repository instead of a specific file, the source browser will be used to display the directory (identical to the result of `source:/some/dir`).

  ==== log: links ====

  The `log:` links are used to display revision ranges. In its simplest form, it can link to the latest revisions from the specified path, but it can also support displaying an arbitrary set of revisions.
   - `log:/` - the latest revisions starting at the root of the repository
   - `log:/trunk/tools` - the latest revisions in `trunk/tools`
   - `log:/trunk/tools@10000` - the revisions in `trunk/tools` starting from  revision 10000
   - `log:@20788,20791:20795` - list revision 20788 and the 20791 to 20795 revision range
   - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from the 20791 to 20795 range which affect the given path

  There are short forms for revision ranges as well:
   - `[20788,20791:20795]`
   - `[20788,20791:20795/trunk/tools]`
   - `r20791:20795` (but not `r20788,20791:20795` nor `r20791:20795/trunk`)

  Finally, note that in all of the above, a revision range can be written indifferently `x:y` or `x-y`.

  ----
  See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki
   


name: TracLogging
author: trac
ipnr: 127.0.0.1
text:
  = Trac Logging =
  [[TracGuideToc]]

  Trac supports logging of system messages using the standard [http://docs.python.org/lib/module-logging.html logging module] that comes with Python.

  Logging is configured in the `[logging]` section in [wiki:TracIni#logging-section trac.ini].

  == Supported Logging Methods ==

  The log method is set using the `log_type` option in [wiki:TracIni#logging-section trac.ini], which takes any of the following values:

   '''none'':: Suppress all log messages.
   '''file''':: Log messages to a file, specified with the `log_file` option in [wiki:TracIni#logging-section trac.ini]. 
   '''stderr''':: Output all log entries to console ([wiki:TracStandalone tracd] only).
   '''syslog''':: (UNIX) Send all log messages to the local syslogd via named pipe `/dev/log`. By default, syslog will write them to the file /var/log/messages.
   '''eventlog''':: (Windows) Use the system's NT Event Log for Trac logging.

  == Log Levels ==

  The verbosity level of logged messages can be set using the `log_level` option in [wiki:TracIni#logging-section trac.ini]. The log level defines the minimum level of urgency required for a message to be logged, and those levels are:

   '''CRITICAL''':: Log only the most critical (typically fatal) errors.
   '''ERROR''':: Log failures, bugs and errors. 
   '''WARN''':: Log warnings, non-interrupting events.
   '''INFO''':: Diagnostic information, log information about all processing.
   '''DEBUG''':: Trace messages, profiling, etc.

  == Log Format ==

  Starting with Trac 0.10.4 (see #2844), it is possible to set the output format for log entries. This can be done through the `log_format` option in [wiki:TracIni#logging-section trac.ini]. The format is a string which can contain any of the [http://docs.python.org/lib/node422.html Python logging Formatter variables]. Additonally, the following Trac-specific variables can be used:
   '''$(basename)s''':: The last path component of the current environment.
   '''$(path)s''':: The absolute path for the current environment.
   '''$(project)s''':: The originating project's name.

  Note that variables are identified using a dollar sign (`$(...)s`) instead of percent sign (`%(...)s`).

  The default format is:
  {{{
  log_format = Trac[$(module)s] $(levelname)s: $(message)s
  }}}

  In a multi-project environment where all logs are sent to the same place (e.g. `syslog`), it makes sense to add the project name. In this example we use `basename` since that can generally be used to identify a project:
  {{{
  log_format = Trac[$(basename)s:$(module)s] $(levelname)s: $(message)s
  }}}

  ----
  See also: TracIni, TracGuide, TracEnvironment


name: TracModPython
author: trac
ipnr: 127.0.0.1
text:
  = Trac and mod_python =
  [[TracGuideToc]]

  Trac supports [http://www.modpython.org/ mod_python], which speeds up Trac's response times considerably, especially compared to [TracCgi CGI], and permits use of many Apache features not possible with [wiki:TracStandalone tracd]/mod_proxy.

  These instructions are for Apache 2; if you are still using Apache 1.3, you may have some luck with [wiki:TracModPython2.7 TracModPython2.7].

  == Simple configuration ==

  If you just installed mod_python, you may have to add a line to load the module in the Apache configuration:
  {{{
  LoadModule python_module modules/mod_python.so
  }}}

  ''Note: The exact path to the module depends on how the HTTPD installation is laid out.''

  On Debian using apt-get
  {{{
  apt-get install libapache2-mod-python libapache2-mod-python-doc
  }}}
  (Still on Debian) after you have installed mod_python, you must enable the modules in apache2 (equivalent of the above Load Module directive):
  {{{
  a2enmod mod_python
  }}}
  On Fedora use, using yum:
  {{{
  yum install mod_python
  }}}
  You can test your mod_python installation by adding the following to your httpd.conf.  You should remove this when you are done testing for security reasons. Note: mod_python.testhandler is only available in mod_python 3.2+.
  {{{
  #!xml
  <Location /mpinfo>
     SetHandler mod_python
     PythonInterpreter main_interpreter
     PythonHandler mod_python.testhandler
  </Location>
  }}}

  A simple setup of Trac on mod_python looks like this:
  {{{
  #!xml
  <Location /projects/myproject>
     SetHandler mod_python
     PythonInterpreter main_interpreter
     PythonHandler trac.web.modpython_frontend 
     PythonOption TracEnv /var/trac/myproject
     PythonOption TracUriRoot /projects/myproject
  </Location>
  }}}

  The option '''`TracUriRoot`''' may or may not be necessary in your setup. Try your configuration without it; if the URLs produced by Trac look wrong, if Trac does not seem to recognize URLs correctly, or you get an odd "No handler matched request to..." error, add the '''`TracUriRoot`''' option.  You will notice that the `Location` and '''`TracUriRoot`''' have the same path.

  The options available are
  {{{
      # For a single project
      PythonOption TracEnv /var/trac/myproject
      # For multiple projects
      PythonOption TracEnvParentDir /var/trac/myprojects
      # For the index of multiple projects
      PythonOption TracEnvIndexTemplate /srv/www/htdocs/trac/project_list_template.html
      # A space delimitted list, with a "," between key and value pairs.
      PythonOption TracTemplateVars key1,val1 key2,val2
      # Useful to get the date in the wanted order
      PythonOption TracLocale en_GB.UTF8
      # See description above        
      PythonOption TracUriRoot /projects/myproject
  }}}

  === Python Egg Cache ===

  Compressed python eggs like Genshi are normally extracted into a directory named `.python-eggs` in the users home directory. Since apache's home usually is not writable an alternate egg cache directory can be specified like this:
  {{{
  PythonOption PYTHON_EGG_CACHE /var/trac/myprojects/egg-cache
  }}}

  === Configuring Authentication ===

  Creating password files and configuring authentication works similar to the process for [wiki:TracCgi#AddingAuthentication CGI]:
  {{{
  #!xml
  <Location /projects/myproject/login>
    AuthType Basic
    AuthName "myproject"
    AuthUserFile /var/trac/myproject/.htpasswd
    Require valid-user
  </Location>
  }}}

  Configuration for mod_ldap authentication in Apache is a bit tricky (httpd 2.2.x and OpenLDAP: slapd 2.3.19)

  1. You need to load the following modules in Apache httpd.conf
  {{{
  LoadModule ldap_module modules/mod_ldap.so
  LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
  }}}

  2. Your httpd.conf also needs to look something like:

  {{{
  #!xml
  <Location /trac/>
    SetHandler mod_python
    PythonInterpreter main_interpreter
    PythonHandler trac.web.modpython_frontend
    PythonOption TracEnv /home/trac/
    PythonOption TracUriRoot /trac/
    Order deny,allow
    Deny from all
    Allow from 192.168.11.0/24
    AuthType Basic
    AuthName "Trac"
    AuthBasicProvider "ldap"
    AuthLDAPURL "ldap://127.0.0.1/dc=example,dc=co,dc=ke?uid?sub?(objectClass=inetOrgPerson)"
    authzldapauthoritative Off
    require valid-user
  </Location>
  }}}

  Or the LDAP interface to a Microsoft Active Directory:

  {{{
  #!xml
  <Location /trac/>
    SetHandler mod_python
    PythonInterpreter main_interpreter
    PythonHandler trac.web.modpython_frontend
    PythonOption TracEnv /home/trac/
    PythonOption TracUriRoot /trac/
    Order deny,allow
    Deny from all
    Allow from 192.168.11.0/24
    AuthType Basic
    AuthName "Trac"
    AuthBasicProvider "ldap"
    AuthLDAPURL "ldap://adserver.company.com:3268/DC=company,DC=com?sAMAccountName?sub?(objectClass=user)"
    AuthLDAPBindDN       ldap-auth-user@company.com
    AuthLDAPBindPassword "the_password"
    authzldapauthoritative Off
    # require valid-user
    require ldap-group CN=Trac Users,CN=Users,DC=company,DC=com
  </Location>
  }}}

  Note 1: This is the case where the LDAP search will get around the multiple OUs, conecting to Global Catalog Server portion of AD (Notice the port is 3268, not the normal LDAP 389). The GCS is basically a "flattened" tree which allows searching for a user without knowing to which OU they belong.

  Note 2: Active Directory requires an authenticating user/password to access records (AuthLDAPBindDN and AuthLDAPBindPassword).

  Note 3: The directive "require ldap-group ..."  specifies an AD group whose members are allowed access.



  === Setting the !PythonPath ===

  If the Trac installation isn't installed in your Python path, you'll have to tell Apache where to find the Trac mod_python handler  using the `PythonPath` directive:
  {{{
  #!xml
  <Location /projects/myproject>
    ...
    PythonPath "sys.path + ['/path/to/trac']"
    ...
  </Location>
  }}}

  Be careful about using the !PythonPath directive, and ''not'' `SetEnv PYTHONPATH`, as the latter won't work.

  == Setting up multiple projects ==

  The Trac mod_python handler supports a configuration option similar to Subversion's `SvnParentPath`, called `TracEnvParentDir`:
  {{{
  #!xml
  <Location /projects>
    SetHandler mod_python
    PythonInterpreter main_interpreter
    PythonHandler trac.web.modpython_frontend 
    PythonOption TracEnvParentDir /var/trac
    PythonOption TracUriRoot /projects
  </Location>
  }}}

  When you request the `/projects` URL, you will get a listing of all subdirectories of the directory you set as `TracEnvParentDir` that look like Trac environment directories. Selecting any project in the list will bring you to the corresponding Trac environment.

  If you don't want to have the subdirectory listing as your projects home page you can use a
  {{{
  #!xml
  <LocationMatch "/.+/">
  }}}

  This will instruct Apache to use mod_python for all locations different from root while having the possibility of placing a custom home page for root in your !DocumentRoot folder.

  You can also use the same authentication realm for all of the projects using a `<LocationMatch>` directive:
  {{{
  #!xml
  <LocationMatch "/projects/[^/]+/login">
    AuthType Basic
    AuthName "Trac"
    AuthUserFile /var/trac/.htpasswd
    Require valid-user
  </LocationMatch>
  }}}

  == Virtual Host Configuration ==

  Below is the sample configuration required to set up your trac as a virtual server (i.e. when you access it at the URLs like
  !http://trac.mycompany.com):

  {{{
  #!xml
  <VirtualHost * >
      DocumentRoot /var/www/myproject
      ServerName trac.mycompany.com
      <Location />
          SetHandler mod_python
          PythonInterpreter main_interpreter
          PythonHandler trac.web.modpython_frontend
          PythonOption TracEnv /var/trac/myproject
          PythonOption TracUriRoot /
      </Location>
      <Location /login>
          AuthType Basic
          AuthName "MyCompany Trac Server"
          AuthUserFile /var/trac/myproject/.htpasswd
          Require valid-user
      </Location>
  </VirtualHost>
  }}}

  This does not seem to work in all cases. What you can do if it does not:
   * Try using `<LocationMatch>` instead of `<Location>`
   * <Location /> may, in your server setup, refer to the complete host instead of simple the root of the server. This means that everything (including the login directory referenced below) will be sent to python and authentication does not work (i.e. you get the infamous Authentication information missing error). If this applies to you, try using a sub-directory for trac instead of the root (i.e. /web/ and /web/login instead of / and /login).

  For a virtual host that supports multiple projects replace "`TracEnv`" /var/trac/myproject with "`TracEnvParentDir`" /var/trac/

  Note: !DocumentRoot should not point to your Trac project env. As Asmodai wrote on #trac: "suppose there's a webserver bug that allows disclosure of !DocumentRoot they could then leech the entire Trac environment".

  == Troubleshooting ==

  In general, if you get server error pages, you can either check the Apache error log, or enable the `PythonDebug` option:
  {{{
  #!xml
  <Location /projects/myproject>
    ...
    PythonDebug on
  </Location>
  }}}

  For multiple projects, try restarting the server as well.

  === Expat-related segmentation faults === #expat

  This problem will most certainly hit you on Unix when using Python 2.4.
  In Python 2.4, some version of Expat (an XML parser library written in C) is used, 
  and if Apache is using another version, this results in segmentation faults.
  As Trac 0.11 is using Genshi, which will indirectly use Expat, that problem
  can now hit you even if everything was working fine before with Trac 0.10.

  See Graham Dumpleton's detailed [http://www.dscpl.com.au/wiki/ModPython/Articles/ExpatCausingApacheCrash explanation and workarounds] for the issue.

  === Form submission problems ===

  If you're experiencing problems submitting some of the forms in Trac (a common problem is that you get redirected to the start page after submission), check whether your {{{DocumentRoot}}} contains a folder or file with the same path that you mapped the mod_python handler to. For some reason, mod_python gets confused when it is mapped to a location that also matches a static resource.

  === Problem with virtual host configuration ===

  If the <Location /> directive is used, setting the `DocumentRoot` may result in a ''403 (Forbidden)'' error. Either remove the `DocumentRoot` directive, or make sure that accessing the directory it points is allowed (in a corresponding `<Directory>` block).

  Using <Location /> together with `SetHandler` resulted in having everything handled by mod_python, which leads to not being able download any CSS or images/icons. I used <Location /trac> `SetHandler None` </Location> to circumvent the problem, though I do not know if this is the most elegant solution.

  === Using .htaccess ===

  Although it may seem trivial to rewrite the above configuration as a directory in your document root with a `.htaccess` file, this does not work. Apache will append a "/" to any Trac URLs, which interferes with its correct operation.

  It may be possible to work around this with mod_rewrite, but I failed to get this working. In all, it is more hassle than it is worth. Stick to the provided instructions. :)

  A success story: For me it worked out-of-box, with following trivial config:
  {{{
  SetHandler mod_python
  PythonInterpreter main_interpreter
  PythonHandler trac.web.modpython_frontend 
  PythonOption TracEnv /system/path/to/this/directory
  PythonOption TracUriRoot /path/on/apache

  AuthType Basic
  AuthName "ProjectName"
  AuthUserFile /path/to/.htpasswd
  Require valid-user
  }}}

  The TracUriRoot is obviously the path you need to enter to the browser to get to the trac (e.g. domain.tld/projects/trac)

  === Additional .htaccess help ===

  If you are using the .htaccess method you may have additional problems if your trac directory is inheriting .htaccess directives from another.  This may also help to add to your .htaccess file:

  {{{
  <IfModule mod_rewrite.c>
    RewriteEngine Off
  </IfModule>
  }}}


  === Win32 Issues ===
  If you run trac with mod_python < 3.2 on Windows, uploading attachments will '''not''' work. This problem is resolved in mod_python 3.1.4 or later, so please upgrade mod_python to fix this.


  === OS X issues ===

  When using mod_python on OS X you will not be able to restart Apache using `apachectl restart`. This is apparently fixed in mod_python 3.2, but there's also a patch available for earlier versions [http://www.dscpl.com.au/projects/vampire/patches.html here].

  === SELinux issues ===

  If Trac reports something like: ''Cannot get shared lock on db.lock''
  The security context on the repository may need to be set:

  {{{
  chcon -R -h -t httpd_sys_content_t PATH_TO_REPOSITORY
  }}}

  See also [[http://subversion.tigris.org/faq.html#reposperms]]

  === FreeBSD issues ===
  Pay attention to the version of the installed mod_python and sqlite packages. Ports have both the new and old ones, but earlier versions of pysqlite and mod_python won't integrate as the former requires threaded support in python, and the latter requires a threadless install.

  If you compiled and installed apache2, apache wouldn´t support threads (cause it doesn´t work very well on FreeBSD). You could force thread support when running ./configure for apache, using --enable-threads, but this isn´t recommendable.
  The best option [[http://modpython.org/pipermail/mod_python/2006-September/021983.html seems to be]] adding to /usr/local/apache2/bin/ennvars the line 

  {{{
  export LD_PRELOAD=/usr/lib/libc_r.so
  }}}

  === Subversion issues ===

  If you get the following Trac Error `Unsupported version control system "svn"` only under mod_python, though it works well on the command-line and even with TracStandalone, chances are that you forgot to add the path to the Python bindings with the [TracModPython#ConfiguringPythonPath PythonPath] directive. (The better way is to add a link to the bindings in the Python `site-packages` directory, or create a `.pth` file in that directory.)

  If this is not the case, it's possible that you're using Subversion libraries that are binary incompatible with the apache ones (an incompatibility of the `apr` libraries is usually the cause). In that case, you also won't be able to use the svn modules for Apache (`mod_dav_svn`).

  You also need a recent version of `mod_python` in order to avoid a runtime error ({{{argument number 2: a 'apr_pool_t *' is expected}}}) due to the default usage of multiple sub-interpreters. 3.2.8 ''should'' work, though it's probably better to use the workaround described in #3371, in order to force the use of the main interpreter:
  {{{
  PythonInterpreter main_interpreter
  }}}
  This is anyway the recommended workaround for other well-known issues seen when using the Python bindings for Subversion within mod_python (#2611, #3455). See in particular Graham Dumpleton's comment in [comment:ticket:3455:9 #3455] explaining the issue.

  === Page layout issues ===

  If the formatting of the Trac pages look weird chances are that the style sheets governing the page layout are not handled properly by the web server. Try adding the following lines to your apache configuration:
  {{{
  #!xml
  Alias /myproject/css "/usr/share/trac/htdocs/css"
  <Location /myproject/css>
      SetHandler None
  </Location>
  }}}

  Note: For the above configuration to have any effect it must be put after the configuration of your project root location, i.e. {{{<Location /myproject />}}}.

  === HTTPS issues ===

  If you want to run Trac fully under https you might find that it tries to redirect to plain http. In this case just add the following line to your apache configuration:
  {{{
  #!xml
  <VirtualHost * >
      DocumentRoot /var/www/myproject
      ServerName trac.mycompany.com
      SetEnv HTTPS 1
      ....
  </VirtualHost>
  }}}

  === Fedora 7 Issues ===
  Make sure you install the 'python-sqlite2' package as it seems to be required for TracModPython but not for tracd


  === Segmentation fault with php5-mhash or other php5 modules ===
  You may encounter segfaults (reported on debian etch) if php5-mhash module is installed. Try to remove it to see if this solves the problem. See debian bug report [[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411487]]

  Some people also have troubles when using php5 compiled with its own 3rd party libraries instead of system libraries. Check here [[http://www.djangoproject.com/documentation/modpython/#if-you-get-a-segmentation-fault]]

  ----
  See also:  TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracFastCgi FastCGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]


name: TracModWSGI
author: trac
ipnr: 127.0.0.1
text:
  = Trac and mod_wsgi =

  '''Important note:''' ''Please use either version 1.3 or 2.3 or later of `mod_wsgi`. Version 2.0 has problems with downloading attachments (see [trac:ticket:7205 #7205]).''

  [http://code.google.com/p/modwsgi/ mod_wsgi] is an Apache module for running WSGI-compatible Python applications directly on top of Apache:

    The mod_wsgi adapter is an Apache module that provides a WSGI compliant interface for hosting Python based web applications within Apache. The adapter is written completely in C code against the Apache C runtime and for hosting WSGI applications within Apache provides significantly better performance than using existing WSGI adapters for mod_python or CGI.

  It is already possible to run Trac on top of mod_wsgi. This can be done by writing the following application script, which is just a Python file, though usually saved with a .wsgi extension).

  {{{
  import os

  os.environ['TRAC_ENV'] = '/usr/local/trac/mysite'
  os.environ['PYTHON_EGG_CACHE'] = '/usr/local/trac/mysite/eggs'

  import trac.web.main
  application = trac.web.main.dispatch_request
  }}}

  The {{{TRAC_ENV}}} variable should naturally be the directory for your Trac environment (if you have several Trac environments in a directory, you can also use {{{TRAC_ENV_PARENT_DIR}}} instead), while the {{{PYTHON_EGG_CACHE}}} should be a directory where Python can temporarily extract Python eggs. [[BR]]
  For clarity, you should give this file a {{{.wsgi}}} extension. You should probably put the file in it's own directory, since you will open up its directory to Apache.
  You can create a .wsgi files which handles all this for you by running the TracAdmin command {{{deploy}}}.

  If you have installed trac and eggs in a path different from the standard one you should add that path by adding the following code on top of the wsgi script:
  {{{
  import site
  site.addsitedir('/usr/local/trac/lib/python2.4/site-packages')
  }}}
  Change it according to the path you installed the trac libs at.

  After you've done preparing your wsgi-script, add the following to your httpd.conf.

  {{{
  WSGIScriptAlias /trac /usr/local/trac/mysite/apache/mysite.wsgi

  <Directory /usr/local/trac/mysite/apache>
      WSGIApplicationGroup %{GLOBAL}
      Order deny,allow
      Allow from all
  </Directory>
  }}}

  Here, the script is in a subdirectory of the Trac environment. In order to let Apache run the script, access to the directory in which the script resides is opened up to all of Apache. Additionally, the {{{WSGIApplicationGroup}}} directive ensures that Trac is always run in the first Python interpreter created by mod_wsgi; this is necessary because the Subversion Python bindings, which are used by Trac, don't always work in other subinterpreters and may cause requests to hang or cause Apache to crash as a result. After adding this configuration, restart Apache, and then it should work.

  To test the setup of Apache, mod_wsgi and Python itself (ie. without involving Trac and dependencies), this simple wsgi application can be used to make sure that requests gets served (use as only content in your .wsgi script):

  {{{
  def application(environ, start_response):
          start_response('200 OK',[('Content-type','text/html')])
          return ['<html><body>Hello World!</body></html>']
  }}}

  See also the mod_wsgi [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac installation instructions] for Trac.

  For troubleshooting tips, see the [TracModPython#Troubleshooting mod_python troubleshooting] section, as most Apache-related issues are quite similar, plus discussion of potential [http://code.google.com/p/modwsgi/wiki/ApplicationIssues application issues] when using mod_wsgi.

  == Trac with PostgreSQL ==

  When using the mod_wsgi adapter with multiple Trac instances and PostgreSQL (or MySQL?) as a database back-end the server can get a lot of open database connections. (and thus PostgreSQL processes)

  A workable solution is to disabled connection pooling in Trac. This is done by setting poolable = False in trac.db.postgres_backend on the PostgreSQLConnection class.

  But it's not necessary to edit the source of trac, the following lines in trac.wsgi will also work:

  {{{
  import trac.db.postgres_backend
  trac.db.postgres_backend.PostgreSQLConnection.poolable = False
  }}}

  Now Trac drops the connection after serving a page and the connection count on the database will be kept minimal.

  == Getting Trac to work nicely with SSPI and 'Require Group' ==
  If like me you've set Trac up on Apache, Win32 and configured SSPI, but added a 'Require group' option to your apache configuration, then the SSPIOmitDomain option is probably not working.  If its not working your usernames in trac are probably looking like 'DOMAIN\user' rather than 'user'.

  This WSGI script 'fixes' things, hope it helps:
  {{{
  import os
  import trac.web.main

  os.environ['TRAC_ENV'] = '/usr/local/trac/mysite'
  os.environ['PYTHON_EGG_CACHE'] = '/usr/local/trac/mysite/eggs'

  def application(environ, start_response):
      if "\\" in environ['REMOTE_USER']:
          environ['REMOTE_USER'] = environ['REMOTE_USER'].split("\\", 1)[1]
      return trac.web.main.dispatch_request(environ, start_response)
  }}}
  ----
  See also:  TracGuide, TracInstall, [wiki:TracFastCgi FastCGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]


name: TracNavigation
author: trac
ipnr: 127.0.0.1
text:
  = Trac Navigation =

  Starting with Trac 0.11, it is now possible to customize the main and meta navigation entries in some basic ways.

  The new `[mainnav]` and `[metanav]` configuration sections can now be used to customize the text and link used for the navigation items, or even to disable them.

  `[mainnav]` corresponds to the '''main navigation bar''', the one containing entries such as ''Wiki'', ''Timeline'', ''Roadmap'', ''Browse Source'' and so on. This navigation bar is meant to access the default page of the main modules enabled in Trac and accessible for the current user.

  `[metanav]` corresponds to the '''meta navigation bar''', by default positioned above the main navigation bar and below the ''Search'' box. It contains the ''Log in'', ''Logout'', ''Help/Guide'' etc. entries. This navigation bar is meant to access some global information about the Trac project and the current user.

  Note that it is still not possible to customize the '''contextual navigation bar''', i.e. the one usually placed below the main navigation bar.

  === Example ===

  In the following example, we rename the link to the Wiki start "Home", and hide the "Help/Guide" link. 
  We also make the "View Tickets" entry link to a specific report.

  Relevant excerpt from the TracIni:
  {{{
  [mainnav]
  wiki.label = Home
  tickets.href = /report/24

  [metanav]
  help = disabled
  }}}

  ----
  See also: TracInterfaceCustomization, and the [http://trac-hacks.org/wiki/NavAddPlugin TracHacks:NavAddPlugin] or [http://trac-hacks.org/wiki/MenusPlugin TracHacks:MenusPlugin] (still needed for adding entries)


name: TracNotification
author: trac
ipnr: 127.0.0.1
text:
  = Email Notification of Ticket Changes =
  [[TracGuideToc]]

  Trac supports notification about ticket changes via email. 

  Email notification is useful to keep users up-to-date on tickets/issues of interest, and also provides a convenient way to post all ticket changes to a dedicated mailing list. For example, this is how the [http://lists.edgewall.com/archive/trac-tickets/ Trac-tickets] mailing list is set up.

  Disabled by default, notification can be activated and configured in [wiki:TracIni trac.ini].

  == Receiving Notification Mails ==
  When reporting a new ticket or adding a comment, enter a valid email address in the ''reporter'', ''assigned to/owner'' or ''cc'' field. Trac will automatically send you an email when changes are made to the ticket (depending on how notification is configured).

  This is useful to keep up-to-date on an issue or enhancement request that interests you.

  == Configuring SMTP Notification ==

  === Configuration Options ===
  These are the available options for the `[notification]` section in trac.ini.

   * '''`smtp_enabled`''': Enable email notification.
   * '''`smtp_from`''': Email address to use for ''Sender''-headers in notification emails.
   * '''`smtp_from_name`''': Sender name to use for ''Sender''-headers in notification emails.
   * '''`smtp_replyto`''': Email address to use for ''Reply-To''-headers in notification emails.
   * '''`smtp_default_domain`''': (''since 0.10'') Append the specified domain to addresses that do not contain one. Fully qualified addresses are not modified. The default domain is appended to all username/login for which an email address cannot be found from the user settings.
   * '''`smtp_always_cc`''': List of email addresses to always send notifications to. ''Typically used to post ticket changes to a dedicated mailing list.''
   * '''`smtp_always_bcc`''': (''since 0.10'') List of email addresses to always send notifications to, but keeps addresses not visible from other recipients of the notification email 
   * '''`smtp_subject_prefix`''': (''since 0.10.1'') Text that is inserted before the subject of the email. Set to "!__default!__" by default.
   * '''`always_notify_reporter`''':  Always send notifications to any address in the reporter field (default: false).
   * '''`always_notify_owner`''': (''since 0.9'') Always send notifications to the address in the owner field (default: false).
   * '''`always_notify_updater`''': (''since 0.10'') Always send a notification to the updater of a ticket (default: true).
   * '''`use_public_cc`''': (''since 0.10'') Addresses in To: (owner, reporter) and Cc: lists are visible by all recipients (default is ''Bcc:'' - hidden copy).
   * '''`use_short_addr`''': (''since 0.10'') Enable delivery of notifications to addresses that do not contain a domain (i.e. do not end with ''@<domain.com>'').This option is useful for intranets, where the SMTP server can handle local addresses and map the username/login to a local mailbox. See also `smtp_default_domain`. Do not use this option with a public SMTP server. 
   * '''`mime_encoding`''': (''since 0.10'') E-mail notifications are always sent in 7-bit mode. This option allows to select the MIME encoding scheme. Supported values:
     * `base64`: default value, works with any kind of content. May cause some issues with touchy anti-spam/anti-virus engines.
     * `qp` or `quoted-printable`: best for european languages (more compact than base64), not recommended for non-ASCII text (less compact than base64)
     * `none`: no encoding. Use with plain english only (ASCII). E-mails with non-ASCII chars won't be delivered. 
   * '''`ticket_subject_template`''': (''since 0.11'') A [http://genshi.edgewall.org/wiki/Documentation/text-templates.html Genshi text template] snippet used to get the notification subject.

  Either '''`smtp_from`''' or '''`smtp_replyto`''' (or both) ''must'' be set, otherwise Trac refuses to send notification mails.

  The following options are specific to email delivery through SMTP.
   * '''`smtp_server`''': SMTP server used for notification messages.
   * '''`smtp_port`''': (''since 0.9'') Port used to contact the SMTP server.
   * '''`smtp_user`''': (''since 0.9'') User name for authentication SMTP account.
   * '''`smtp_password`''': (''since 0.9'') Password for authentication SMTP account.
   * '''`use_tls`''': (''since 0.10'') Toggle to send notifications via a SMTP server using [http://en.wikipedia.org/wiki/Transport_Layer_Security TLS], such as GMail.


  === Example Configuration (SMTP) ===
  {{{
  [notification]
  smtp_enabled = true
  smtp_server = mail.example.com
  smtp_from = notifier@example.com
  smtp_replyto = myproj@projects.example.com
  smtp_always_cc = ticketmaster@example.com, theboss+myproj@example.com
  }}}


  === Customizing the e-mail subject ===
  The e-mail subject can be customized with the `ticket_subject_template` option, which contains a [http://genshi.edgewall.org/wiki/Documentation/text-templates.html Genshi text template] snippet. The default value is:
  {{{
  $prefix #$ticket.id: $summary
  }}}
  The following variables are available in the template:

   * `env`: The project environment (see [trac:source:/trunk/trac/env.py env.py]).
   * `prefix`: The prefix defined in `smtp_subject_prefix`.
   * `summary`: The ticket summary, with the old value if the summary was edited.
   * `ticket`: The ticket model object (see [trac:source:/trunk/trac/ticket/model.py model.py]). Individual ticket fields can be addressed by appending the field name separated by a dot, e.g. `$ticket.milestone`.

  == Sample Email ==
  {{{
  #42: testing
  ---------------------------+------------------------------------------------
         Id:  42             |      Status:  assigned                
  Component:  report system  |    Modified:  Fri Apr  9 00:04:31 2004
   Severity:  major          |   Milestone:  0.9                     
   Priority:  lowest         |     Version:  0.6                     
      Owner:  anonymous      |    Reporter:  jonas@example.com               
  ---------------------------+------------------------------------------------
  Changes:
    * component:  changset view => search system
    * priority:  low => highest
    * owner:  jonas => anonymous
    * cc:  daniel@example.com =>
           daniel@example.com, jonas@example.com
    * status:  new => assigned

  Comment:
  I'm interested too!

  --
  Ticket URL: <http://example.com/trac/ticket/42>
  My Project <http://myproj.example.com/>
  }}}

  == Using GMail as the SMTP relay host ==

  Use the following configuration snippet
  {{{
  [notification]
  smtp_enabled = true
  use_tls = true
  mime_encoding = base64
  smtp_server = smtp.gmail.com
  smtp_port = 587
  smtp_user = user
  smtp_password = password
  }}}

  where ''user'' and ''password'' match an existing GMail account, ''i.e.'' the ones you use to log in on [http://gmail.com]

  Alternatively, you can use `smtp_port = 25`.[[br]]
  You should not use `smtp_port = 465`. It will not work and your ticket submission may deadlock. Port 465 is reserved for the SMTPS protocol, which is not supported by Trac. See [comment:ticket:7107:2 #7107] for details.
   
  == Filtering notifications for one's own changes ==
  In Gmail, use the filter:

  {{{
  from:(<smtp_from>) (("Reporter: <username>" -Changes) OR "Changes (by <username>)")
  }}}

  to delete these notifications.

  In Thunderbird, there is no such solution if you use IMAP
  (see http://kb.mozillazine.org/Filters_(Thunderbird)#Filtering_the_message_body).

  The best you can do is to set "always_notify_updater" in conf/trac.ini to false.
  You will however still get an email if you comment a ticket that you own or have reported.

  You can also add this plugin:
  http://trac-hacks.org/wiki/NeverNotifyUpdaterPlugin

  == Troubleshooting ==

  If you cannot get the notification working, first make sure the log is activated and have a look at the log to find if an error message has been logged. See TracLogging for help about the log feature.

  Notification errors are not reported through the web interface, so the user who submit a change or a new ticket never gets notified about a notification failure. The Trac administrator needs to look at the log to find the error trace.

  === ''Permission denied'' error ===

  Typical error message:
  {{{
    ...
    File ".../smtplib.py", line 303, in connect
      raise socket.error, msg
    error: (13, 'Permission denied')
  }}}

  This error usually comes from a security settings on the server: many Linux distributions do not let the web server (Apache, ...) to post email message to the local SMTP server.

  Many users get confused when their manual attempts to contact the SMTP server succeed:
  {{{
  telnet localhost 25
  }}}
  The trouble is that a regular user may connect to the SMTP server, but the web server cannot:
  {{{
  sudo -u www-data telnet localhost 25
  }}}

  In such a case, you need to configure your server so that the web server is authorized to post to the SMTP server. The actual settings depend on your Linux distribution and current security policy. You may find help browsing the Trac [trac:MailingList MailingList] archive.

  Relevant ML threads:
   * SELinux: http://article.gmane.org/gmane.comp.version-control.subversion.trac.general/7518
   
  === ''Suspected spam'' error ===

  Some SMTP servers may reject the notification email sent by Trac.

  The default Trac configuration uses Base64 encoding to send emails to the recipients. The whole body of the email is encoded, which sometimes trigger ''false positive'' SPAM detection on sensitive email servers. In such an event, it is recommended to change the default encoding to "quoted-printable" using the `mime_encoding` option.

  Quoted printable encoding works better with languages that use one of the Latin charsets. For Asian charsets, it is recommended to stick with the Base64 encoding.

  ----
  See also: TracTickets, TracIni, TracGuide


name: TracPermissions
author: trac
ipnr: 127.0.0.1
text:
  = Trac Permissions =
  [[TracGuideToc]]

  Trac uses a simple, case sensitive, permission system to control what users can and can't access.

  Permission privileges are managed using the [TracAdmin trac-admin] tool or (new in version 0.11) the ''General / Permissions'' panel in the ''Admin'' tab of the web interface.

  In addition to the default permission policy described in this page, it is possible to activate additional permission policies by enabling plugins and listing them in the `[trac] permission_policies` configuration entry in the TracIni. See TracFineGrainedPermissions for more details.

  Non-authenticated users accessing the system are assigned the name "anonymous". Assign permissions to the "anonymous" user to set privileges for anonymous/guest users. The parts of Trac that a user does not have the privileges for will not be displayed in the navigation.
  In addition to these privileges, users can be granted additional individual rights in effect when authenticated and logged into the system. All logged in users belong to the virtual group "authenticated", which inherits permissions from "anonymous".

  == Graphical Admin Tab ==
  ''This feature is new in version 0.11.''

  To access this tab, a user must have `TRAC_ADMIN privileges`. This can be performed as follows (more on the trac-admin script below):
  {{{
    $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN
  }}}

  Then, the user will be able to see the Admin tab, and can then access the permissions menu. This menu will allow you to perform all the following actions, but from the browser without requiring root access to the server (just the correct permissions for your user account).


  An easy way to quickly secure a new Trac install is to run the above command on the anonymous user, install the [http://trac-hacks.org/wiki/AccountManagerPlugin AccountManagerPlugin], create a new admin account graphically and then remove the TRAC_ADMIN permission from the anonymous user.

  == Available Privileges ==

  To enable all privileges for a user, use the `TRAC_ADMIN` permission. Having `TRAC_ADMIN` is like being `root` on a *NIX system: it will allow you to perform any operation.

  Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac ('''note that the privilege names are case-sensitive'''):

  === Repository Browser ===

  || `BROWSER_VIEW` || View directory listings in the [wiki:TracBrowser repository browser] ||
  || `LOG_VIEW` || View revision logs of files and directories in the [wiki:TracBrowser repository browser] ||
  || `FILE_VIEW` || View files in the [wiki:TracBrowser repository browser] ||
  || `CHANGESET_VIEW` || View [wiki:TracChangeset repository check-ins] ||

  === Ticket System ===

  || `TICKET_VIEW` || View existing [wiki:TracTickets tickets] and perform [wiki:TracQuery ticket queries] ||
  || `TICKET_CREATE` || Create new [wiki:TracTickets tickets] ||
  || `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] ||
  || `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties (priority, assignment, keywords, etc.) except description field, cc field add/remove when logged in or set email to pref ||
  || `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets] ||
  || `TICKET_EDIT_CC` || Full modify cc field ||
  || `TICKET_EDIT_DESCRIPTION` || Modify description field ||
  || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the description field ||

  Attention: the "view tickets" button appears with the `REPORT_VIEW` permission.

  === Roadmap ===

  || `MILESTONE_VIEW` || View a milestone ||
  || `MILESTONE_CREATE` || Create a new milestone ||
  || `MILESTONE_MODIFY` || Modify existing milestones ||
  || `MILESTONE_DELETE` || Delete milestones ||
  || `MILESTONE_ADMIN` || All `MILESTONE_*` permissions ||
  || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see #4292 ||
  || `ROADMAP_ADMIN` || to be removed with #3022, replaced by MILESTONE_ADMIN ||

  === Reports ===

  || `REPORT_VIEW` || View [wiki:TracReports reports], i.e. the "view tickets" link. ||
  || `REPORT_SQL_VIEW` || View the underlying SQL query of a [wiki:TracReports report] ||
  || `REPORT_CREATE` || Create new [wiki:TracReports reports] ||
  || `REPORT_MODIFY` || Modify existing [wiki:TracReports reports] ||
  || `REPORT_DELETE` || Delete [wiki:TracReports reports] ||
  || `REPORT_ADMIN` || All `REPORT_*` permissions ||

  === Wiki System ===

  || `WIKI_VIEW` || View existing [wiki:TracWiki wiki] pages ||
  || `WIKI_CREATE` || Create new [wiki:TracWiki wiki] pages ||
  || `WIKI_MODIFY` || Change [wiki:TracWiki wiki] pages ||
  || `WIKI_DELETE` || Delete [wiki:TracWiki wiki] pages and attachments ||
  || `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. ||

  === Permissions ===

  || `PERMISSION_GRANT` || add/grant a permission ||
  || `PERMISSION_REVOKE` || remove/revoke a permission ||
  || `PERMISSION_ADMIN` || All `PERMISSION_*` permissions ||


  === Others ===

  || `TIMELINE_VIEW` || View the [wiki:TracTimeline timeline] page ||
  || `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries ||
  || `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins ||
  || `EMAIL_VIEW` || Shows email addresses even if [wiki:0.11/TracIni `trac show_email_addresses` configuration option is `false`] ||

  == Granting Privileges ==

  You grant privileges to users using [wiki:TracAdmin trac-admin]. The current set of privileges can be listed with the following command:
  {{{
    $ trac-admin /path/to/projenv permission list
  }}}

  This command will allow the user ''bob'' to delete reports:
  {{{
    $ trac-admin /path/to/projenv permission add bob REPORT_DELETE
  }}}

  The `permission add` command also accepts multiple privilege names:
  {{{
    $ trac-admin /path/to/projenv permission add bob REPORT_DELETE WIKI_CREATE
  }}}

  Or add all privileges:
  {{{
    $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN
  }}}

  == Permission Groups ==

  There are two built-in groups, "authenticated" and "anonymous".[[BR]]
  Any user who has not logged in is automatically in the "anonymous" group.[[BR]]
  Any user who has logged in is also in the "authenticated" group.[[BR]]
  The "authenticated" group inherits permissions from the "anonymous" group.[[BR]]
  eg. if the "anonymous" group has permission WIKI_MODIFY, it's not necessary to add the WIKI_MODIFY permisison to the "authenticated" group as well.

  Custom groups may be defined that inherit permissions from the two built-in groups.

  Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc.
  {{{
    $ trac-admin /path/to/projenv permission add developer WIKI_ADMIN
    $ trac-admin /path/to/projenv permission add developer REPORT_ADMIN
    $ trac-admin /path/to/projenv permission add developer TICKET_MODIFY
    $ trac-admin /path/to/projenv permission add bob developer
    $ trac-admin /path/to/projenv permission add john developer
  }}}

  Group membership can be checked by doing a {{{permission list}}} with no further arguments; the resulting output will include group memberships. '''Use lowercase for group names, as uppercase is reserved for permissions'''.

  == Adding a New Group and Permissions ==
  Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group.

  The following will add ''bob'' to the new group called ''beta_testers'' and then will assign WIKI_ADMIN permissions to that group. (Thus, ''bob'' will inherit the WIKI_ADMIN permission)
  {{{ 
     $ trac-admin /path/to/projenv permission add bob beta_testers
     $ trac-admin /path/to/projenv permission add beta_testers WIKI_ADMIN

  }}}

  == Removing Permissions ==

  Permissions can be removed using the 'remove' command. For example:

  This command will prevent the user ''bob'' from deleting reports:
  {{{
    $ trac-admin /path/to/projenv permission remove bob REPORT_DELETE
  }}}

  Just like `permission add`, this command accepts multiple privilege names.

  You can also remove all privileges for a specific user:
  {{{
    $ trac-admin /path/to/projenv permission remove bob '*'
  }}}

  Or one privilege for all users:
  {{{
    $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN
  }}}

  == Default Permissions ==

  By default on a new Trac installation, the `anonymous` user will have ''view'' access to everything in Trac, but will not be able to create or modify anything.
  On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''.

   '''anonymous'''::
   BROWSER_VIEW 
   CHANGESET_VIEW 
   FILE_VIEW 
   LOG_VIEW 
   MILESTONE_VIEW 
   REPORT_SQL_VIEW 
   REPORT_VIEW 
   ROADMAP_VIEW 
   SEARCH_VIEW 
   TICKET_VIEW 
   TIMELINE_VIEW
   WIKI_VIEW 

   '''authenticated'''::
   TICKET_CREATE 
   TICKET_MODIFY 
   WIKI_CREATE 
   WIKI_MODIFY  

  ----
  See also: TracAdmin, TracGuide and TracFineGrainedPermissions


name: TracPlugins
author: trac
ipnr: 127.0.0.1
text:
  = Trac Plugins =
  [[TracGuideToc]]

  Since version 0.9, Trac supports [trac:PluginList plugins] that extend the built-in functionality. The plugin functionality is based on the [trac:TracDev/ComponentArchitecture component architecture].

  == Requirements ==

  To use egg based plugins in Trac, you need to have [http://peak.telecommunity.com/DevCenter/setuptools setuptools] (version 0.6) installed.

  To install `setuptools`, download the bootstrap module [http://peak.telecommunity.com/dist/ez_setup.py ez_setup.py] and execute it as follows:
  {{{
  $ python ez_setup.py
  }}}

  If the `ez_setup.py` script fails to install the setuptools release, you can download it from [http://www.python.org/pypi/setuptools PyPI] and install it manually.

  Plugins can also consist of a single `.py` file dropped into either the environment or global `plugins` directory ''(since [milestone:0.10])''. See TracIni#GlobalConfiguration .

  == Installing a Trac Plugin ==

  === For a Single Project ===

  Plugins are packaged as [http://peak.telecommunity.com/DevCenter/PythonEggs Python eggs]. That means they are ZIP archives with the file extension `.egg`. 

  If you have downloaded a source distribution of a plugin, and want to build the `.egg` file, follow this instruction:
   * Unpack the source. It should provide a setup.py. 
   * Run:
  {{{
  $ python setup.py bdist_egg
  }}}

  Then you will have a *.egg file. Examine the output of running python to find where this was created.

  Once you have the plugin archive, you need to copy it into the `plugins` directory of the [wiki:TracEnvironment project environment]. Also, make sure that the web server has sufficient permissions to read the plugin egg.

  To uninstall a plugin installed this way, remove the egg from `plugins` directory and restart web server.

  Note that the Python version that the egg is built with must
  match the Python version with which Trac is run.  If for
  instance you are running Trac under Python 2.3, but have
  upgraded your standalone Python to 2.4, the eggs won't be
  recognized.

  Note also that in a multi-project setup, a pool of Python interpreter instances will be dynamically allocated to projects based on need, and since plugins occupy a place in Python's module system, the first version of any given plugin to be loaded will be used for all the projects. In other words, you cannot use different versions of a single plugin in two projects of a multi-project setup. It may be safer to install plugins for all projects (see below) and then enable them selectively on a project-by-project basis.

  === For All Projects ===

  ==== With an .egg file ====

  Some plugins (such as [trac:SpamFilter SpamFilter]) are downloadable as a `.egg` file which can be installed with the `easy_install` program:
  {{{
  easy_install TracSpamFilter
  }}}

  If `easy_install` is not on your system see the Requirements section above to install it.  Windows users will need to add the `Scripts` directory of their Python installation (for example, `C:\Python23\Scripts`) to their `PATH` environment variable (see [http://peak.telecommunity.com/DevCenter/EasyInstall#windows-notes easy_install Windows notes] for more information).

  If Trac reports permission errors after installing a zipped egg and you would rather not bother providing a egg cache directory writable by the web server, you can get around it by simply unzipping the egg. Just pass `--always-unzip` to `easy_install`:
  {{{
  easy_install --always-unzip TracSpamFilter-0.2.1dev_r5943-py2.4.egg
  }}}
  You should end up with a directory having the same name as the zipped egg (complete with `.egg` extension) and containing its uncompressed contents.

  Trac also searches for globally installed plugins ''(since 0.10)'', see TracIni#GlobalConfiguration.

  ==== From source ====

  `easy_install` makes installing from source a snap. Just give it the URL to either a Subversion repository or a tarball/zip of the source:
  {{{
  easy_install http://svn.edgewall.com/repos/trac/sandbox/spam-filter
  }}}

  ==== Enabling the plugin ====
  Unlike plugins installed per-environment, you'll have to explicitly enable globally installed plugins via [wiki:TracIni trac.ini]. This also applies to plugins installed in the path specified in the `[inherit] plugins_dir` configuration option. This is done in the `[components]` section of the configuration file, for example:
  {{{
  [components]
  tracspamfilter.* = enabled
  }}}

  The name of the option is the Python package of the plugin. This should be specified in the documentation of the plugin, but can also be easily discovered by looking at the source (look for a top-level directory that contains a file named `__init__.py`.)

  Note: After installing the plugin, you need to restart your web server.

  ==== Uninstalling ====

  `easy_install` or `python setup.py` does not have an uninstall feature. Hower, it is usually quite trivial to remove a globally installed egg and reference:
   1. Do `easy_install -m [plugin name]` to remove references from `$PYTHONLIB/site-packages/easy-install.pth` when the plugin installed by setuptools.
   1. Delete executables from `/usr/bin`, `/usr/local/bin` or `C:\\Python*\Scripts`. For search what executables are there, you may refer to `[console-script]` section of `setup.py`.
   1. Delete the .egg file or folder from where it is installed, usually inside `$PYTHONLIB/site-packages/`.
   1. Restart web server.

  If you are uncertain about the location of the egg, here is a small tip to help locate an egg (or any package) - replace `myplugin` with whatever namespace the plugin uses (as used when enabling the plugin):
  {{{
  >>> import myplugin
  >>> print myplugin.__file__
  /opt/local/python24/lib/site-packages/myplugin-0.4.2-py2.4.egg/myplugin/__init__.pyc
  }}}

  == Setting up the Plugin Cache ==

  Some plugins will need to be extracted by the Python eggs runtime (`pkg_resources`), so that their contents are actual files on the file system. The directory in which they are extracted defaults to '.python-eggs' in the home directory of the current user, which may or may not be a problem. You can however override the default location using the `PYTHON_EGG_CACHE` environment variable.

  To do this from the Apache configuration, use the `SetEnv` directive as follows:
  {{{
  SetEnv PYTHON_EGG_CACHE /path/to/dir
  }}}

  This works whether you are using the [wiki:TracCgi CGI] or the [wiki:TracModPython mod_python] front-end. Put this directive next to where you set the path to the [wiki:TracEnvironment Trac environment], i.e. in the same `<Location>` block.

  For example (for CGI):
  {{{
   <Location /trac>
     SetEnv TRAC_ENV /path/to/projenv
     SetEnv PYTHON_EGG_CACHE /path/to/dir
   </Location>
  }}}

  or (for mod_python):
  {{{
   <Location /trac>
     SetHandler mod_python
     ...
     SetEnv PYTHON_EGG_CACHE /path/to/dir
   </Location>
  }}}

   ''Note: !SetEnv requires the `mod_env` module which needs to be activated for Apache. In this case the !SetEnv directive can also be used in the `mod_python` Location block.''

  For [wiki:TracFastCgi FastCGI], you'll need to `-initial-env` option, or whatever is provided by your web server for setting environment variables. 

   ''Note: that if you already use -initial-env to set the project directory for either a single project or parent you will need to add an additional -initial-env directive to the !FastCgiConfig directive. I.e.

  {{{
  FastCgiConfig -initial-env TRAC_ENV=/var/lib/trac -initial-env PYTHON_EGG_CACHE=/var/lib/trac/plugin-cache
  }}}

  === About hook scripts ===

  If you have set up some subversion hook scripts that call the Trac engine - such as the post-commit hook script provided in the `/contrib` directory - make sure you define the `PYTHON_EGG_CACHE` environment variable within these scripts as well.

  == Troubleshooting ==

  === Is setuptools properly installed? ===

  Try this from the command line:
  {{{
  $ python -c "import pkg_resources"
  }}}

  If you get '''no output''', setuptools '''is''' installed. Otherwise, you'll need to install it before plugins will work in Trac.

  === Did you get the correct version of the Python egg? ===

  Python eggs have the Python version encoded in their filename. For example, `MyPlugin-1.0-py2.4.egg` is an egg for Python 2.4, and will '''not''' be loaded if you're running a different Python version (such as 2.3 or 2.5).

  Also, verify that the egg file you downloaded is indeed a ZIP archive. If you downloaded it from a Trac site, chances are you downloaded the HTML preview page instead.

  === Is the plugin enabled? ===


  If you install a plugin globally (i.e. ''not'' inside the `plugins` directory of the Trac project environment) you will have to explicitly enable it in [TracIni trac.ini]. Make sure that:
   * you actually added the necessary line(s) to the `[components]` section
   * the package/module names are correct
   * the value is “enabled", not e.g. “enable”

  === Check the permissions on the egg file ===

  Trac must be able to read the file. 

  === Check the log files ===

  Enable [wiki:TracLogging logging] and set the log level to `DEBUG`, then watch the log file for messages about loading plugins.

  === Verify you have proper permissions ===

  Some plugins require you have special permissions in order to use them. [trac:WebAdmin WebAdmin], for example, requires the user to have TRAC_ADMIN permissions for it to show up on the navigation bar.

  === Is the wrong version of the plugin loading? ===

  If you put your plugins inside plugins directories, and certainly if you have more than one project, you need to make sure that the correct version of the plugin is loading. Here are some basic rules:
   * Only one version of the plugin can be loaded for each running Trac server (ie. each Python process). The Python namespaces and module list will be shared, and it cannot handle duplicates. Whether a plugin is `enabled` or `disabled` makes no difference.
   * A globally installed plugin (typically `setup.py install`) will override any version in global or project plugins directories. A plugin from the global plugins directory will be located before any project plugins directory.
   * If your Trac server hosts more than one project (as with `TRAC_ENV_PARENT_DIR` setups), then having two versions of a plugin in two different projects will give uncertain results. Only one of them will load, and the one loaded will be shared by both projects. Trac will load the first found - basically from the project that receives the first request.
   * Having more than one version listed inside Python site-packages is fine (ie. installed with `setup.py install`) - setuptools will make sure you get the version installed most recently. However, don't store more than one version inside a global or project plugins directory - neither version number nor installed date will matter at all. There is no way to determine which one will be located first when Trac searches the directory for plugins.

  === If all of the above failed ===

  OK, so the logs don't mention plugins, the egg is readable, the python version is correct ''and'' the egg has been installed globally (and is enabled in the trac.ini) and it still doesn't work or give any error messages or any other indication as to why? Hop on the [trac:IrcChannel IrcChannel] and ask away.

  ----
  See also TracGuide, [trac:PluginList plugin list], [trac:TracDev/ComponentArchitecture component architecture]


name: TracQuery
author: trac
ipnr: 127.0.0.1
text:
  = Trac Ticket Queries =
  [[TracGuideToc]]

  In addition to [wiki:TracReports reports], Trac provides support for ''custom ticket queries'', used to display lists of tickets meeting a specified set of criteria. 

  To configure and execute a custom query, switch to the ''View Tickets'' module from the navigation bar, and select the ''Custom Query'' link.

  == Filters ==
  When you first go to the query page the default filters will display all open tickets, or if you're logged in it will display open tickets assigned to you.  Current filters can be removed by clicking the button to the right with the minus sign on the label.  New filters are added from the pulldown list in the bottom-right corner of the filters box.  Filters with either a text box or a pulldown menu of options can be added multiple times to perform an ''or'' of the criteria.

  You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket.

  Once you've edited your filters click the ''Update'' button to refresh your results.

  == Navigating Tickets ==
  Clicking on one of the query results will take you to that ticket.  You can navigate through the results by clicking the ''Next Ticket'' or ''Previous Ticket'' links just below the main menu bar, or click the ''Back to Query'' link to return to the query page.  

  You can safely edit any of the tickets and continue to navigate through the results using the ''Next/Previous/Back to Query'' links after saving your results.  When you return to the query ''any tickets which were edited'' will be displayed with italicized text.  If one of the tickets was edited such that [[html(<span style="color: grey">it no longer matches the query criteria </span>)]] the text will also be greyed. Lastly, if '''a new ticket matching the query criteria has been created''', it will be shown in bold. 

  The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again.

  == Saving Queries ==

  While Trac does not yet allow saving a named query and somehow making it available in a navigable list, you can save references to queries in Wiki content, as described below.

  === Using TracLinks ===

  You may want to save some queries so that you can come back to them later.  You can do this by making a link to the query from any Wiki page.
  {{{
  [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
  }}}

  Which is displayed as:
    [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]

  This uses a very simple query language to specify the criteria (see [wiki:TracQuery#QueryLanguage Query Language]).

  Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading `?` character:
  {{{
  [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
  }}}

  Which is displayed as:
    [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]

  === Using the `[[TicketQuery]]` Macro ===

  The [trac:TicketQuery TicketQuery] macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.

  Example:
  {{{
  [[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
  }}}

  This is displayed as:
    [[TicketQuery(version=0.6|0.7&resolution=duplicate)]]

  Just like the [wiki:TracQuery#UsingTracLinks query: wiki links], the parameter of this macro expects a query string formatted according to the rules of the simple [wiki:TracQuery#QueryLanguage ticket query language].

  A more compact representation without the ticket summaries is also available:
  {{{
  [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
  }}}

  This is displayed as:
    [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]

  Finally if you wish to receive only the number of defects that match the query using the ``count`` parameter.

  {{{
  [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
  }}}

  This is displayed as:
    [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]

  === Customizing the ''table'' format ===
  You can also customize the columns displayed in the table format (''format=table'') by using ''col=<field>'' - you can specify multiple fields and what order they are displayed by placing pipes (`|`) between the columns like below:

  {{{
  [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]
  }}}

  This is displayed as:
  [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]


  === Query Language ===

  `query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Basically, the filters are separated by ampersands (`&`). Each filter then consists of the ticket field name, an operator, and one or more values. More than one value are separated by a pipe (`|`), meaning that the filter matches any of the values.

  The available operators are:
  || '''`=`''' || the field content exactly matches the one of the values ||
  || '''`~=`''' || the field content contains one or more of the values ||
  || '''`^=`''' || the field content starts with one of the values ||
  || '''`$=`''' || the field content ends with one of the values ||

  All of these operators can also be negated:
  || '''`!=`''' || the field content matches none of the values ||
  || '''`!~=`''' || the field content does not contain any of the values ||
  || '''`!^=`''' || the field content does not start with any of the values ||
  || '''`!$=`''' || the field content does not end with any of the values ||


  ----
  See also: TracTickets, TracReports, TracGuide


name: TracReports
author: trac
ipnr: 127.0.0.1
text:
  = Trac Reports =
  [[TracGuideToc]]

  The Trac reports module provides a simple, yet powerful reporting facility
  to present information about tickets in the Trac database.

  Rather than have its own report definition format, TracReports relies on standard SQL
  `SELECT` statements for custom report definition. 

    '''Note:''' ''The report module is being phased out in its current form because it seriously limits the ability of the Trac team to make adjustments to the underlying database schema. We believe that the [wiki:TracQuery query module] is a good replacement that provides more flexibility and better usability. While there are certain reports that cannot yet be handled by the query module, we intend to further enhance it so that at some point the reports module can be completely removed. This also means that there will be no major enhancements to the report module anymore.''

    ''You can already completely replace the reports module by the query module simply by disabling the former in [wiki:TracIni trac.ini]:''
    {{{
    [components]
    trac.ticket.report.* = disabled
    }}}
    ''This will make the query module the default handler for the “View Tickets” navigation item. We encourage you to try this configuration and report back what kind of features of reports you are missing, if any.''

    '''''You will almost definitely need to restart your httpd at this point.'''''

  A report consists of these basic parts:
   * '''ID''' -- Unique (sequential) identifier 
   * '''Title'''  -- Descriptive title
   * '''Description'''  -- A brief description of the report, in WikiFormatting text.
   * '''Report Body''' -- List of results from report query, formatted according to the methods described below.
   * '''Footer''' -- Links to alternative download formats for this report.

  == Changing Sort Order ==
  Simple reports - ungrouped reports to be specific - can be changed to be sorted by any column simply by clicking the column header. 

  If a column header is a hyperlink (red), click the column you would like to sort by. Clicking the same header again reverses the order.

  == Changing Report Numbering ==
  There may be instances where you need to change the ID of the report, perhaps to organize the reports better. At present this requires changes to the trac database. The ''report'' table has the following schema (as of 0.10):
   * id integer PRIMARY KEY
   * author text
   * title text
   * query text
   * description text
  Changing the ID changes the shown order and number in the ''Available Reports'' list and the report's perma-link. This is done by running something like:
  {{{
  update report set id=5 where id=3;
  }}}
  Keep in mind that the integrity has to be maintained (i.e., ID has to be unique, and you don't want to exceed the max, since that's managed by SQLite someplace).

  == Navigating Tickets ==
  Clicking on one of the report results will take you to that ticket. You can navigate through the results by clicking the ''Next Ticket'' or ''Previous Ticket'' links just below the main menu bar, or click the ''Back to Report'' link to return to the report page.

  You can safely edit any of the tickets and continue to navigate through the results using the Next/Previous/Back to Report links after saving your results, but when you return to the report, there will be no hint about what has changed, as would happen if you were navigating a list of tickets obtained from a query (see TracQuery#NavigatingTickets). ''(since 0.11)''

  == Alternative Download Formats ==
  Aside from the default HTML view, reports can also be exported in a number of alternative formats.
  At the bottom of the report page, you will find a list of available data formats. Click the desired link to 
  download the alternative report format.

  === Comma-delimited - CSV (Comma Separated Values) ===
  Export the report as plain text, each row on its own line, columns separated by a single comma (',').
  '''Note:''' Carriage returns, line feeds, and commas are stripped from column data to preserve the CSV structure.

  === Tab-delimited ===
  Like above, but uses tabs (\t) instead of comma.

  === RSS - XML Content Syndication ===
  All reports support syndication using XML/RSS 2.0. To subscribe to an RSS feed, click the orange 'XML' icon at the bottom of the page. See TracRss for general information on RSS support in Trac.

  ----

  == Creating Custom Reports ==

  ''Creating a custom report requires a comfortable knowledge of SQL.''

  A report is basically a single named SQL query, executed and presented by
  Trac.  Reports can be viewed and created from a custom SQL expression directly
  in from the web interface.

  Typically, a report consists of a SELECT-expression from the 'ticket' table,
  using the available columns and sorting the way you want it.

  == Ticket columns ==
  The ''ticket'' table has the following columns:
   * id
   * type
   * time
   * changetime
   * component
   * severity  
   * priority 
   * owner
   * reporter
   * cc
   * version
   * milestone
   * status
   * resolution
   * summary
   * description
   * keywords

  See TracTickets for a detailed description of the column fields.

  '''all active tickets, sorted by priority and time'''

  '''Example:''' ''All active tickets, sorted by priority and time''
  {{{
  SELECT id AS ticket, status, severity, priority, owner, 
         time as created, summary FROM ticket 
    WHERE status IN ('new', 'assigned', 'reopened')
    ORDER BY priority, time
  }}}


  ----


  == Advanced Reports: Dynamic Variables ==
  For more flexible reports, Trac supports the use of ''dynamic variables'' in report SQL statements. 
  In short, dynamic variables are ''special'' strings that are replaced by custom data before query execution.

  === Using Variables in a Query ===
  The syntax for dynamic variables is simple, any upper case word beginning with '$' is considered a variable.

  Example:
  {{{
  SELECT id AS ticket,summary FROM ticket WHERE priority=$PRIORITY
  }}}

  To assign a value to $PRIORITY when viewing the report, you must define it as an argument in the report URL, leaving out the leading '$'.

  Example:
  {{{
   http://trac.edgewall.org/reports/14?PRIORITY=high
  }}}

  To use multiple variables, separate them with an '&'.

  Example:
  {{{
   http://trac.edgewall.org/reports/14?PRIORITY=high&SEVERITY=critical
  }}}


  === Special/Constant Variables ===
  There is one ''magic'' dynamic variable to allow practical reports, its value automatically set without having to change the URL. 

   * $USER -- Username of logged in user.

  Example (''List all tickets assigned to me''):
  {{{
  SELECT id AS ticket,summary FROM ticket WHERE owner=$USER
  }}}


  ----


  == Advanced Reports: Custom Formatting ==
  Trac is also capable of more advanced reports, including custom layouts,
  result grouping and user-defined CSS styles. To create such reports, we'll use
  specialized SQL statements to control the output of the Trac report engine.

  == Special Columns ==
  To format reports, TracReports looks for 'magic' column names in the query
  result. These 'magic' names are processed and affect the layout and style of the 
  final report.

  === Automatically formatted columns ===
   * '''ticket''' -- Ticket ID number. Becomes a hyperlink to that ticket. 
   * '''created, modified, date, time''' -- Format cell as a date and/or time.

   * '''description''' -- Ticket description field, parsed through the wiki engine.

  '''Example:'''
  {{{
  SELECT id as ticket, created, status, summary FROM ticket 
  }}}

  === Custom formatting columns ===
  Columns whose names begin and end with 2 underscores (Example: '''`__color__`''') are
  assumed to be ''formatting hints'', affecting the appearance of the row.
   
   * '''`__group__`''' -- Group results based on values in this column. Each group will have its own header and table.
   * '''`__color__`''' -- Should be a numeric value ranging from 1 to 5 to select a pre-defined row color. Typically used to color rows by issue priority.
  {{{
  #!html
  <div style="margin-left:7.5em">Defaults: 
  <span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #fdc; border-color: #e88; color: #a22">Color 1</span>
  <span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #ffb; border-color: #eea; color: #880">Color 2</span>
  <span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #fbfbfb; border-color: #ddd; color: #444">Color 3</span>
  <span style="border: none; color: #333; background: transparent; font-size: 85%; background: #e7ffff; border-color: #cee; color: #099">Color 4</span>
  <span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #e7eeff; border-color: #cde; color: #469">Color 5</span>
  </div>
  }}}
   * '''`__style__`''' -- A custom CSS style expression to use for the current row. 

  '''Example:''' ''List active tickets, grouped by milestone, colored by priority''
  {{{
  SELECT p.value AS __color__,
       t.milestone AS __group__,
       (CASE owner WHEN 'daniel' THEN 'font-weight: bold; background: red;' ELSE '' END) AS __style__,
         t.id AS ticket, summary
    FROM ticket t,enum p
    WHERE t.status IN ('new', 'assigned', 'reopened') 
      AND p.name=t.priority AND p.type='priority'
    ORDER BY t.milestone, p.value, t.severity, t.time
  }}}

  '''Note:''' A table join is used to match ''ticket'' priorities with their
  numeric representation from the ''enum'' table.

  === Changing layout of report rows ===
  By default, all columns on each row are display on a single row in the HTML
  report, possibly formatted according to the descriptions above. However, it's
  also possible to create multi-line report entries.

   * '''`column_`''' -- ''Break row after this''. By appending an underscore ('_') to the column name, the remaining columns will be be continued on a second line.

   * '''`_column_`''' -- ''Full row''. By adding an underscore ('_') both at the beginning and the end of a column name, the data will be shown on a separate row.

   * '''`_column`'''  --  ''Hide data''. Prepending an underscore ('_') to a column name instructs Trac to hide the contents from the HTML output. This is useful for information to be visible only if downloaded in other formats (like CSV or RSS/XML).

  '''Example:''' ''List active tickets, grouped by milestone, colored by priority, with  description and multi-line layout''

  {{{
  SELECT p.value AS __color__,
         t.milestone AS __group__,
         (CASE owner 
            WHEN 'daniel' THEN 'font-weight: bold; background: red;' 
            ELSE '' END) AS __style__,
         t.id AS ticket, summary AS summary_,             -- ## Break line here
         component,version, severity, milestone, status, owner,
         time AS created, changetime AS modified,         -- ## Dates are formatted
         description AS _description_,                    -- ## Uses a full row
         changetime AS _changetime, reporter AS _reporter -- ## Hidden from HTML output
    FROM ticket t,enum p
    WHERE t.status IN ('new', 'assigned', 'reopened') 
      AND p.name=t.priority AND p.type='priority'
    ORDER BY t.milestone, p.value, t.severity, t.time
  }}}

  === Reporting on custom fields ===

  If you have added custom fields to your tickets (a feature since v0.8, see TracTicketsCustomFields), you can write a SQL query to cover them. You'll need to make a join on the ticket_custom table, but this isn't especially easy.

  If you have tickets in the database ''before'' you declare the extra fields in trac.ini, there will be no associated data in the ticket_custom table. To get around this, use SQL's "LEFT OUTER JOIN" clauses. See [trac:TracIniReportCustomFieldSample TracIniReportCustomFieldSample] for some examples.

  '''Note that you need to set up permissions in order to see the buttons for adding or editing reports.'''

  ----
  See also: TracTickets, TracQuery, TracGuide, [http://www.sqlite.org/lang_expr.html Query Language Understood by SQLite]


