You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by rj...@apache.org on 2014/11/14 12:06:31 UTC
svn commit: r1639602 [12/14] - in /bloodhound/vendor/trac/current: ./
contrib/workflow/ doc/dev/ sample-plugins/ sample-plugins/permissions/
sample-plugins/workflow/ trac/ trac/admin/ trac/admin/templates/
trac/admin/tests/ trac/db/ trac/db/tests/ trac...
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracBackup
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracBackup?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracBackup (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracBackup Fri Nov 14 11:06:23 2014
@@ -8,17 +8,15 @@ Since Trac uses a database backend, some
== Creating a Backup ==
To create a backup of a live TracEnvironment, simply run:
-{{{
-
- $ trac-admin /path/to/projenv hotcopy /path/to/backupdir
-
+ {{{#!sh
+$ 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].
+Please note, the `hotcopy` command will not overwrite a target directory and when such exists the operation ends with error: `Command failed: [Errno 17] File exists:` This is discussed in [trac:ticket:3198 #3198].
=== Restoring a Backup ===
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracBatchModify
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracBatchModify?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracBatchModify (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracBatchModify Fri Nov 14 11:06:23 2014
@@ -1,10 +1,14 @@
= Trac Ticket Batch Modification =
[[TracGuideToc]]
-From [wiki:TracQuery custom query] results Trac provides support for modifying a batch of tickets in one request.
+From [TracQuery custom query] results Trac provides support for modifying a batch of tickets in one request.
To perform a batch modification select the tickets you wish to modify and set the new field values using the section underneath the query results.
== List fields
The `Keywords` and `Cc` fields are treated as lists, where list items can be added and/or removed in addition of replacing the entire list value. All list field controls accept multiple items (i.e. multiple keywords or cc addresses).
+
+== Excluded fields
+
+Multi-line text fields are not supported, because no valid use-case has been presented for syncing them across several tickets. That restriction applies to the `Description` field as well as to any [TracTicketsCustomFields#AvailableFieldTypesandOptions custom field] of type 'textarea'. However in conjunction with more suitable actions like 'prepend', 'append' or search & replace ([http://trac-hacks.org/ticket/2415 th:#2415]) this could change in future Trac versions.
\ No newline at end of file
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracBrowser
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracBrowser?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracBrowser (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracBrowser Fri Nov 14 11:06:23 2014
@@ -52,20 +52,15 @@ for more advanced cases.
If you're using a Javascript enabled browser, you'll be able to expand and
collapse directories in-place by clicking on the arrow head at the right side of a
directory. Alternatively, the [trac:TracKeys keyboard] can also be used for this:
- - use `'j'` and `'k'` to select the next or previous entry, starting with the first
- - `'o'` (open) to toggle between expanded and collapsed state of the selected
+ - use `j` and `k` to select the next or previous entry, starting with the first
+ - `o` ('''o'''pen) to toggle between expanded and collapsed state of the selected
directory or for visiting the selected file
- - `'v'` (view, visit) and `'<Enter>'`, same as above
- - `'r'` can be used to force the reload of an already expanded directory
- - `'A'` can be used to directly visit a file in annotate (blame) mode
- - `'L'` to view the log for the selected entry
-If no row has been selected using `'j'` or `'k'` these keys will operate on the entry under the mouse.
+ - `v` ('''v'''iew, '''v'''isit) and `<Enter>`, same as above
+ - `r` can be used to force the '''r'''eload of an already expanded directory
+ - `a` can be used to directly visit a file in '''a'''nnotate (blame) mode
+ - `l` to view the '''l'''og for the selected entry
+If no row has been selected using `j` or `k` these keys will operate on the entry under the mouse.
-{{{#!comment
-MMM: I guess that some keys are upper case and some lower to avoid conflicts with browser defined keys.
-I find for example in Firefox and IE on windows that 'a' works as well as 'A' but 'l' does not work for 'L'.
- cboos: 'l' is reserved for Vim like behavior, see #7867
-}}}
For the Subversion backend, some advanced additional features are available:
- The `svn:needs-lock` property will be displayed
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracCgi
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracCgi?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracCgi (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracCgi Fri Nov 14 11:06:23 2014
@@ -1,39 +1,38 @@
-= Installing Trac as CGI =
+= Installing Trac as CGI
-{{{
-#!div class=important
+{{{#!div class=important
''Please note that using Trac via CGI is the slowest deployment method available. It is slower than [TracModPython mod_python], [TracFastCgi FastCGI] and even [trac:TracOnWindowsIisAjp IIS/AJP] on Windows.''
}}}
CGI script is the entrypoint that web-server calls when a web-request to an application is made. To generate the `trac.cgi` script run:
-{{{
+{{{#!sh
trac-admin /path/to/env deploy /path/to/www/trac
}}}
`trac.cgi` will be in the `cgi-bin` folder inside the given path. ''Make sure it is executable by your web server''. This command also copies `static resource` files to a `htdocs` directory of a given destination.
-== Apache web-server configuration ==
+== Apache web-server configuration
In [http://httpd.apache.org/ Apache] there are two ways to run Trac as CGI:
1. Use a `ScriptAlias` directive that maps an URL to the `trac.cgi` script (recommended)
- 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.
+ 1. 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.
To make Trac available at `http://yourhost.example.org/trac` add `ScriptAlias` directive to Apache configuration file, changing `trac.cgi` path to match your installation:
-{{{
+{{{#!sh
ScriptAlias /trac /path/to/www/trac/cgi-bin/trac.cgi
}}}
''Note that this directive requires enabled `mod_alias` module.''
If you're using Trac with a single project you need to set its location using the `TRAC_ENV` environment variable:
-{{{
+{{{#!apache
<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:
-{{{
+{{{#!apache
<Location "/trac">
SetEnv TRAC_ENV_PARENT_DIR "/path/to/project/parent/dir"
</Location>
@@ -41,31 +40,31 @@ Or to use multiple projects you can spec
''Note that the `SetEnv` directive requires enabled `mod_env` module. It is also possible to set TRAC_ENV in trac.cgi. Just add the following code between "try:" and "from trac.web ...":''
-{{{
+{{{#!python
import os
os.environ['TRAC_ENV'] = "/path/to/projectenv"
}}}
'' Or for TRAC_ENV_PARENT_DIR: ''
-{{{
+{{{#!python
import os
os.environ['TRAC_ENV_PARENT_DIR'] = "/path/to/project/parent/dir"
}}}
-If you are using the [http://httpd.apache.org/docs/suexec.html Apache suEXEC] feature please see [http://trac.edgewall.org/wiki/ApacheSuexec].
+If you are using the [http://httpd.apache.org/docs/suexec.html Apache suEXEC] feature please see [trac: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).
-=== Using WSGI ===
+=== Using WSGI
You can run a [http://henry.precheur.org/python/how_to_serve_cgi WSGI handler] [http://pythonweb.org/projects/webmodules/doc/0.5.3/html_multipage/lib/example-webserver-web-wsgi-simple-cgi.html under CGI]. You can [wiki:TracModWSGI#Thetrac.wsgiscript write your own application function], or use the deployed trac.wsgi's application.
-== Mapping Static Resources ==
+== Mapping Static Resources
See TracInstall#MappingStaticResources.
-== Adding Authentication ==
+== Adding Authentication
See TracInstall#ConfiguringAuthentication.
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracEnvironment
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracEnvironment?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracEnvironment (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracEnvironment Fri Nov 14 11:06:23 2014
@@ -13,6 +13,9 @@ $ trac-admin /path/to/myproject initenv
database connection string (explained below).
=== Some Useful Tips
+
+ - Place your environment's directory on a filesystem which supports sub-second timestamps, as Trac monitors the timestamp of its configuration files and changes happening on a filesystem with too coarse-grained timestamp resolution may go undetected in Trac < 1.0.2 (this is also true for the location of authentication files when using TracStandalone).
+
- The user under which the web server runs 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 source code repository,
@@ -35,6 +38,8 @@ to use SQLite, which is probably suffici
file is then stored in the environment directory, and can easily be
[wiki:TracBackup backed up] together with the rest of the environment.
+Note that if the username or password of the connection string (if applicable) contains the `:`, `/` or `@` characters, they need to be URL encoded.
+
=== SQLite Connection String ===
The connection string for an SQLite database is:
{{{
@@ -50,7 +55,6 @@ user `johndoe` with the password `letmei
{{{
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:
{{{
@@ -91,9 +95,8 @@ postgres://user:pass@server/database?sch
=== 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
+The format of the MySQL connection string is similar to the examples presented for PostgreSQL, with the `postgres` schema being replaced by `mysql`. For example, to connect to a MySQL
+database on the same machine called `trac`, allowing access to the
user `johndoe` with the password `letmein`, the mysql connection string is:
{{{
mysql://johndoe:letmein@localhost:3306/trac
@@ -153,4 +156,4 @@ It happens that the structure for a Trac
structure, but those are two disjoint entities and they are not and ''must not'' be located at the same place.
----
-See also: TracAdmin, TracBackup, TracIni, TracGuide
+See also: TracAdmin, TracBackup, TracIni, TracGuide
\ No newline at end of file
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracFastCgi
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracFastCgi?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracFastCgi (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracFastCgi Fri Nov 14 11:06:23 2014
@@ -370,7 +370,7 @@ http://yourdomain.com/trac/
Nginx is able to communicate with FastCGI processes, but can not spawn them. So you need to start FastCGI server for Trac separately.
1. Nginx configuration with basic authentication handled by Nginx - confirmed to work on 0.6.32
-{{{
+ {{{
server {
listen 10.9.8.7:443;
server_name trac.example;
@@ -414,7 +414,7 @@ Nginx is able to communicate with FastCG
# WSGI application name - trac instance prefix.
# (Or ``fastcgi_param SCRIPT_NAME /some/prefix``.)
fastcgi_param SCRIPT_NAME "";
- fastcgi_param PATH_INFO $path_info;
+ fastcgi_param PATH_INFO $fastcgi_script_name;
## WSGI NEEDED VARIABLES - trac warns about them
fastcgi_param REQUEST_METHOD $request_method;
@@ -437,10 +437,8 @@ Nginx is able to communicate with FastCG
}
}
}}}
-
- 2. Modified trac.fcgi:
-
-{{{
+ 1. Modified trac.fcgi:
+ {{{
#!/usr/bin/env python
import os
sockaddr = '/home/trac/run/instance.sock'
@@ -471,10 +469,8 @@ except Exception, e:
print tb.getvalue()
}}}
-
- 3. reload nginx and launch trac.fcgi like that:
-
-{{{
+ 1. reload nginx and launch trac.fcgi like that:
+ {{{#!sh
trac@trac.example ~ $ ./trac-standalone-fcgi.py
}}}
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracFineGrainedPermissions
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracFineGrainedPermissions?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracFineGrainedPermissions (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracFineGrainedPermissions Fri Nov 14 11:06:23 2014
@@ -16,9 +16,9 @@ Which policies are currently active is d
e.g.
{{{
[trac]
-permission_policies = AuthzSourcePolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
+permission_policies = ReadonlyWikiPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
}}}
-This lists the [#AuthzSourcePolicy] described below as the first policy, followed by the !DefaultPermissionPolicy which checks for the traditional coarse grained style permissions described in TracPermissions, and the !LegacyAttachmentPolicy which knows how to use the coarse grained permissions for checking the permissions available on attachments.
+This lists the [#ReadonlyWikiPolicy] which controls readonly access to wiki pages, followed by the !DefaultPermissionPolicy which checks for the traditional coarse grained style permissions described in TracPermissions, and the !LegacyAttachmentPolicy which knows how to use the coarse grained permissions for checking the permissions available on attachments.
Among the possible optional choices, there is [#AuthzPolicy], a very generic permission policy, based on an Authz-style system. See
[trac:source:branches/0.12-stable/tracopt/perm/authz_policy.py authz_policy.py] for details.
@@ -30,15 +30,15 @@ See also [trac:source:branches/0.12-stab
=== !AuthzPolicy ===
==== Configuration ====
-* Install [http://www.voidspace.org.uk/python/configobj.html ConfigObj] (still needed for 0.12).
-* Copy authz_policy.py into your plugins directory (only for Trac 0.11).
+* Install [http://www.voidspace.org.uk/python/configobj.html ConfigObj] (still needed for 0.12 and later).
+* Copy [browser:/trunk/tracopt/perm/authz_policy.py /tracopt/perm/authz_policy.py] to your environment's plugins directory (only for Trac 0.11).
* 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. If the file contains non-ASCII characters, the UTF-8 encoding should be used.
* Update your `trac.ini`:
1. modify the [TracIni#trac-section permission_policies] entry in the `[trac]` section
{{{
[trac]
...
-permission_policies = AuthzPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
+permission_policies = AuthzPolicy, ReadonlyWikiPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
}}}
1. add a new `[authz_policy]` section
{{{
@@ -90,14 +90,14 @@ jack = WIKI_VIEW
[wiki:WikiStart]
}}}
- Example: Match the attachment `wiki:WikiStart@117/attachment/FOO.JPG@*`
+ Example: Match the attachment `wiki:WikiStart@117/attachment:FOO.JPG@*`
on WikiStart
{{{
[wiki:*]
[wiki:WikiStart*]
[wiki:WikiStart@*]
-[wiki:WikiStart@*/attachment/*]
-[wiki:WikiStart@117/attachment/FOO.JPG]
+[wiki:WikiStart@*/attachment:*]
+[wiki:WikiStart@117/attachment:FOO.JPG]
}}}
* Sections are checked against the current Trac resource descriptor '''IN ORDER''' of
@@ -160,10 +160,15 @@ Some repository examples (Browse Source
john = BROWSER_VIEW, FILE_VIEW
# John has BROWSER_VIEW and FILE_VIEW for the entire test_repo
+# The default repository (requires Trac 1.0.2 or later):
+[repository:@*]
+john = BROWSER_VIEW, FILE_VIEW
+# John has BROWSER_VIEW and FILE_VIEW for the entire default repository
+
# All repositories:
[repository:*@*]
jack = BROWSER_VIEW, FILE_VIEW
-# John has BROWSER_VIEW and FILE_VIEW for all repositories
+# Jack has BROWSER_VIEW and FILE_VIEW for all repositories
}}}
Very fine grain repository access:
@@ -271,7 +276,7 @@ As of version 0.12, make sure you have '
{{{
[trac]
-permission_policies = AuthzSourcePolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
+permission_policies = AuthzSourcePolicy, ReadonlyWikiPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
}}}
==== Subversion Configuration ====
@@ -289,6 +294,35 @@ The same access file is typically applie
For information about how to restrict access to entire projects in a multiple project environment see [trac:wiki:TracMultipleProjectsSVNAccess]
+=== ReadonlyWikiPolicy
+
+Since 1.1.2, the read-only attribute of wiki pages is enabled and enforced when `ReadonlyWikiPolicy` is in the list of active permission policies. The default for new Trac installations in 1.1.2 and later is:
+{{{
+[trac]
+permission_policies = ReadonlyWikiPolicy,
+ DefaultPermissionPolicy,
+ LegacyAttachmentPolicy
+}}}
+
+When upgrading from earlier versions of Trac, `ReadonlyWikiPolicy` will be appended to the list of `permission_policies` when upgrading the environment, provided that `permission_policies` has the default value. If any non-default `permission_polices` are active, `ReadonlyWikiPolicy` **will need to be manually added** to the list. A message will be echoed to the console when upgrading the environment, indicating if any action needs to be taken.
+
+**!ReadonlyWikiPolicy must be listed //before// !DefaultPermissionPolicy**. The latter returns `True` to allow modify, delete or rename actions when the user has the respective `WIKI_*` permission, without consideration for the read-only attribute.
+
+The `ReadonlyWikiPolicy` returns `False` to deny modify, delete and rename actions on wiki pages when the page has the read-only attribute set and the user does not have `WIKI_ADMIN`, regardless of `WIKI_MODIFY`, `WIKI_DELETE` and `WIKI_RENAME` permissions. It returns `None` for all other cases.
+
+When active, the [#AuthzPolicy] should therefore come before `ReadonlyWikiPolicy`, allowing it to grant or deny the actions on individual resources, which is the usual ordering for `AuthzPolicy` in the `permission_policies` list.
+{{{
+[trac]
+permission_policies = AuthzPolicy,
+ ReadonlyWikiPolicy,
+ DefaultPermissionPolicy,
+ LegacyAttachmentPolicy
+}}}
+
+The placement of [#AuthzSourcePolicy] relative to `ReadonlyWikiPolicy` does not matter since they don't perform checks on the same realms.
+
+For all other permission policies, the user will need to decide the proper ordering. Generally, if the permission policy should be capable of overriding the check performed by `ReadonlyWikiPolicy`, it should come before `ReadonlyWikiPolicy` in the list. If the `ReadonlyWikiPolicy` should override the check performed by another permission policy, as is the case for `DefaultPermissionPolicy`, then `ReadonlyWikiPolicy` should come first.
+
== Debugging permissions
In trac.ini set:
{{{
@@ -305,7 +339,6 @@ tail -n 0 -f log/trac.log | egrep '\[per
to understand what checks are being performed. See the sourced documentation of the plugin for more info.
-
----
See also: TracPermissions,
[http://trac-hacks.org/wiki/FineGrainedPageAuthzEditorPlugin TracHacks:FineGrainedPageAuthzEditorPlugin] for a simple editor plugin.
\ No newline at end of file
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracGuide
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracGuide?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracGuide (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracGuide Fri Nov 14 11:06:23 2014
@@ -60,4 +60,4 @@ Trac allows wiki markup in issue descrip
* [trac:TracDev] and [trac:TracDev/ApiDocs API docs] â Trac Developer documentation
* TracSupport â How to get more 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.
+If you are looking for a good place to ask a question about Trac, look no further than the [trac:MailingList MailingList]. It provides a friendly environment to discuss openly among Trac users and developers.
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracImport
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracImport?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracImport (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracImport Fri Nov 14 11:06:23 2014
@@ -18,7 +18,7 @@ Below, follows a collection of some of t
[http://trac-hacks.org/wiki/BugzillaIssueTrackingPlugin BugzillaIssueTrackingPlugin] :: integrates Bugzilla into Trac keeping TracLinks
-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.
+Ticket data can be imported from Bugzilla using the [trac:browser:trunk/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the contrib/ directory of the Trac distribution.
{{{
$ bugzilla2trac.py
@@ -83,14 +83,14 @@ For more details on the available option
[http://trac-hacks.org/wiki/SfnToTracScript SfnToTracScript] :: importer of !SourceForge's new backup file (originated from #Trac3521)
-Also, 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.
+Also, ticket data can be imported from Sourceforge using the [trac:browser:trunk/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution.
== 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.
=== Comma delimited file - CSV ===
-See [http://trac.edgewall.org/attachment/wiki/TracSynchronize/csv2trac.2.py 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)
+See [trac:attachment:csv2trac.2.py: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)
Comments on script: The script has an error on line 168, ('Ticket' needs to be 'ticket'). Also, the listed values for severity and priority are swapped.
----
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracIni
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracIni?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracIni (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracIni Fri Nov 14 11:06:23 2014
@@ -11,7 +11,7 @@ The `trac.ini` configuration file and it
== Global Configuration ==
-In versions prior to 0.11, the global configuration was by default located in `$prefix/share/trac/conf/trac.ini` or /etc/trac/trac.ini, depending on the distribution. If you're upgrading, you may want to specify that file to inherit from. Literally, when you're upgrading to 0.11, you have to add an `[inherit]` section to your project's `trac.ini` file. Additionally, you have to move your customized templates and common images from `$prefix/share/trac/...` to the new location.
+In versions prior to 0.11, the global configuration was by default located in `$prefix/share/trac/conf/trac.ini` or `/etc/trac/trac.ini`, depending on the distribution. If you're upgrading, you may want to specify that file to inherit from. Literally, when you're upgrading to 0.11, you have to add an `[inherit]` section to your project's `trac.ini` file. Additionally, you have to move your customized templates and common images from `$prefix/share/trac/...` to the new location.
Global options will be merged with the environment-specific options, where local options override global options. The options file is specified as follows:
{{{
@@ -30,7 +30,21 @@ Note that the templates found in the `te
This is a brief reference of available configuration options, and their default settings.
+ ''Note that the [hg], [spam-filter], [translatedpages], [vote], [wikiextras] and [wikiextras-symbols] sections below are added by plugins enabled on this Trac, and therefore won't be part of a default installation.''
+
+{{{
+#!comment
+Suggest your documentation fixes in the Discussion section at
+the bottom of the page, or better send us patches against
+the corresponding docstrings you'll find in the code!
+
+Please don't waste your time by editing the HTML code below, changes won't be picked up.
+}}}
[[TracIni]]
+== Discussion ==
+''Please discuss documentation changes here. Even better, send us documentation patches against the code, either on Trac-dev or on new tickets.''
+
+
----
See also: TracGuide, TracAdmin, TracEnvironment
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracInstall
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracInstall?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracInstall (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracInstall Fri Nov 14 11:06:23 2014
@@ -1,24 +1,30 @@
-= Trac Installation Guide for 1.0 =
+{{{#!div style="margin-top: .5em; padding: 0 1em; background-color: #ffd; border:1px outset #ddc; text-align: center"
+
+ '''NOTE: the information in this page applies to Trac 1.0, the current version of Trac. \\
+ For installing previous Trac versions, please refer to [[wiki:0.12/TracInstall]] (for Trac 0.12)'''
+}}}
+
+= Trac Installation Guide for 1.0
[[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.
-Since version 0.12, Trac can also be localized, and there's probably a translation available for your language. If you want to be able to use the Trac interface in other languages, then make sure you have installed the optional package [#OtherPythonPackages Babel]. Pay attention to the extra steps for localization support in the [#InstallingTrac Installing Trac] section below. Lacking Babel, you will only get the default english version, as usual.
+Since version 0.12, Trac can also be localized, and there's probably a translation available for your language. If you want to be able to use the Trac interface in other languages, then make sure you have installed the optional package [#OtherPythonPackages Babel]. Pay attention to the extra steps for localization support in the [#InstallingTrac Installing Trac] section below. Lacking Babel, you will only get the default English version, as usual.
-If you're interested in contributing new translations for other languages or enhance the existing translations, then please have a look at [[trac:TracL10N]].
+If you're interested in contributing new translations for other languages or enhance the existing translations, then please have a look at [trac:wiki:TracL10N TracL10N].
What follows are generic instructions for installing and setting up Trac and its requirements. While you may find instructions for installing Trac on specific systems at [trac: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.
[[PageOutline(2-3,Installation Steps,inline)]]
-== Dependencies ==
+== Dependencies
=== Mandatory Dependencies
To install Trac, the following software packages must be installed:
* [http://www.python.org/ Python], version >= 2.5 and < 3.0
(note that we dropped the support for Python 2.4 in this release)
- * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.6, or better yet, [http://pypi.python.org/pypi/distribute distribute]
- * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6 (unreleased version 0.7dev should work as well)
+ * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.6
+ * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6
You also need a database system and the corresponding python bindings.
The database can be either SQLite, PostgreSQL or MySQL.
@@ -27,10 +33,10 @@ The database can be either SQLite, Postg
As you must be using Python 2.5, 2.6 or 2.7, you already have the SQLite database bindings bundled with the standard distribution of Python (the `sqlite3` module).
-However, if you'd like, you can download the latest and greatest version of [[trac:Pysqlite]] from
+However, if you'd like, you can download the latest and greatest version of [[trac:PySqlite]] from
[http://code.google.com/p/pysqlite/downloads/list google code], where you'll find the Windows
installers or the `tar.gz` archive for building from source:
-{{{
+{{{#!sh
$ tar xvfz <version>.tar.gz
$ cd <version>
$ python setup.py build_static install
@@ -40,7 +46,7 @@ This will download the latest SQLite cod
SQLite 2.x is no longer supported.
-A known bug PySqlite versions 2.5.2-4 prohibits upgrade of trac databases
+A known bug in PySqlite versions 2.5.2-4 prohibits upgrades of Trac databases
from 0.11.x to 0.12. Please use versions 2.5.5 and newer or 2.5.1 and
older. See #9434 for more detail.
@@ -50,7 +56,7 @@ See additional information in [trac:PySq
You need to install the database and its Python bindings:
* [http://www.postgresql.org/ PostgreSQL], version 8.0 or later
- * [http://pypi.python.org/pypi/psycopg2 psycopg2]
+ * [http://pypi.python.org/pypi/psycopg2 psycopg2], version 2.0 or later
See [trac:DatabaseBackend#Postgresql DatabaseBackend] for details.
@@ -66,9 +72,9 @@ It is '''very''' important to read caref
=== Optional Dependencies
-==== Version Control System ====
+==== Version Control System
-===== Subversion =====
+===== Subversion
* [http://subversion.apache.org/ Subversion], 1.5.x or 1.6.x and the '''''corresponding''''' Python bindings. Older versions starting from 1.0, like 1.2.4, 1.3.2 or 1.4.2, etc. should still work. For troubleshooting information, check the [trac:TracSubversion#Troubleshooting TracSubversion] page.
There are [http://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. (Good luck finding precompiled SWIG bindings for any Windows package at that listing. TracSubversion points you to [http://alagazam.net Algazam], which works for me under Python 2.6.)
@@ -79,18 +85,18 @@ Note that Trac '''doesn't''' use [http:/
'''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported].
-===== Others =====
+===== Others
Support for other version control systems is provided via third-parties. See [trac:PluginList] and [trac:VersionControlSystem].
-==== Web Server ====
-A web server is optional because Trac is shipped with a server included, see the [#RunningtheStandaloneServer Running the Standalone Server ] section below.
+==== Web Server
+A web server is optional because Trac is shipped with a server included, see the [#RunningtheStandaloneServer Running the Standalone Server] section below.
-Alternatively you configure Trac to run in any of the following environments.
+Alternatively you can configure Trac to run in any of the following environments.
* [http://httpd.apache.org/ Apache] with
- [http://code.google.com/p/modwsgi/ mod_wsgi], see [wiki:TracModWSGI] and
http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac
- - [http://modpython.org/ mod_python 3.3.1], deprecated: see TracModPython)
+ - [http://modpython.org/ mod_python 3.3.1], (deprecated: see TracModPython)
* a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi)
* an [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web
server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp])
@@ -98,13 +104,13 @@ Alternatively you configure Trac to run
is highly discouraged''', better use one of the previous options.
-==== Other Python Packages ====
+==== Other Python Packages
* [http://babel.edgewall.org Babel], version >= 0.9.5,
needed for localization support (unreleased version 1.0dev should work as well)
* [http://docutils.sourceforge.net/ docutils], version >= 0.3.9
for WikiRestructuredText.
- * [http://pygments.pocoo.org Pygments] for
+ * [http://pygments.org Pygments] for
[wiki:TracSyntaxColoring syntax highlighting].
[http://silvercity.sourceforge.net/ SilverCity] and/or
[http://gnu.org/software/enscript/enscript.html Enscript] may still be used
@@ -113,106 +119,109 @@ Alternatively you configure Trac to run
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] or [trac:IrcChannel].
+'''Attention''': The various available versions of these dependencies are not necessarily interchangeable, 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] or [trac: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 ==
+== Installing Trac
=== Using `easy_install`
One way to install Trac is using [http://pypi.python.org/pypi/setuptools setuptools].
-With setuptools you can install Trac from the subversion repository;
+With setuptools you can install Trac from the Subversion repository;
A few examples:
- - install Trac 1.0:
- {{{
+ - Install Trac 1.0:
+ {{{#!sh
easy_install Trac==1.0
}}}
- (NOT YET ENABLED)
- - install latest development version 1.0dev:
- {{{
+ - Install latest development version:
+ {{{#!sh
easy_install Trac==dev
}}}
Note that in this case you won't have the possibility to run a localized version of Trac;
either use a released version or install from source
+{{{#!div style="border: 1pt dotted; margin: 1em"
+**Setuptools Warning:** If the version of your setuptools is in the range 5.4 through 5.6, the environment variable `PKG_RESOURCES_CACHE_ZIP_MANIFESTS` must be set in order to avoid significant performance degradation. More information may be found in the sections on [#RunningtheStandaloneServer Running The Standalone Server] and [#RunningTraconaWebServer Running Trac on a Web Server].
+}}}
+
=== Using `pip`
'pip' is an easy_install replacement that is very useful to quickly install python packages.
-To get a trac installation up and running in less than 5 minutes:
+To get a Trac installation up and running in less than 5 minutes:
Assuming you want to have your entire pip installation in `/opt/user/trac`
-
-{{{
-pip -E /opt/user/trac install trac psycopg2
+ {{{#!sh
+pip install trac psycopg2
}}}
or
-
-{{{
-pip -E /opt/user/trac install trac mysql-python
+ {{{#!sh
+pip install trac mysql-python
}}}
-Make sure your OS specific headers are available for pip to automatically build PostgreSQL (libpq-dev) or MySQL (libmysqlclient-dev) bindings.
+Make sure your OS specific headers are available for pip to automatically build PostgreSQL (`libpq-dev`) or MySQL (`libmysqlclient-dev`) bindings.
pip will automatically resolve all dependencies (like Genshi, pygments, etc.) and download the latest packages on pypi.python.org and create a self contained installation in `/opt/user/trac`.
All commands (`tracd`, `trac-admin`) are available in `/opt/user/trac/bin`. This can also be leveraged for `mod_python` (using `PythonHandler` directive) and `mod_wsgi` (using `WSGIDaemonProcess` directive)
-Additionally, you can install several trac plugins (listed [http://pypi.python.org/pypi?:action=search&term=trac&submit=search here]) through pip.
+Additionally, you can install several Trac plugins (listed [http://pypi.python.org/pypi?:action=search&term=trac&submit=search here]) through pip.
=== From source
Of course, using the python-typical setup at the top of the source directory also works.
-You can obtain the source for a .tar.gz or .zip file corresponding to a release (e.g. Trac-1.0.tar.gz), or you can get the source directly from the repository (see Trac:SubversionRepository for details).
+You can obtain the source for a .tar.gz or .zip file corresponding to a release (e.g. `Trac-1.0.tar.gz`), or you can get the source directly from the repository (see [trac:SubversionRepository] for details).
-{{{
+{{{#!sh
$ python ./setup.py install
}}}
''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.
+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.
-If you install from source and want to make Trac available in other languages, make sure Babel is installed. Only then, perform the `install` (or simply redo the `install` once again afterwards if you realize Babel was not yet installed):
-{{{
+If you install from source and want to make Trac available in other languages, make sure Babel is installed. Only then, perform the `install` (or simply redo the `install` once again afterwards if you realize Babel was not yet installed):
+{{{#!sh
$ python ./setup.py install
}}}
-Alternatively, you can do a `bdist_egg` and copy the .egg from dist/ to the place of your choice, or you can create a Windows installer (`bdist_wininst`).
+Alternatively, you can run `bdist_egg` and copy the .egg from `dist/` to the place of your choice, or you can create a Windows installer (`bdist_wininst`).
-=== Advanced Options ===
+=== Advanced Options
To install Trac to a custom location, or find out about other advanced installation options, run:
-{{{
+{{{#!sh
easy_install --help
}}}
-Also see [http://docs.python.org/inst/inst.html Installing Python Modules] for detailed information.
+Also see [http://docs.python.org/2/install/index.html Installing Python Modules] for detailed information.
Specifically, you might be interested in:
-{{{
+{{{#!sh
easy_install --prefix=/path/to/installdir
}}}
-or, if installing Trac to a Mac OS X system:
-{{{
+or, if installing Trac on a Mac OS X system:
+{{{#!sh
easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages
}}}
-Note: If installing on Mac OS X 10.6 running {{{ easy_install http://svn.edgewall.org/repos/trac/trunk }}} will install into {{{ /usr/local }}} and {{{ /Library/Python/2.6/site-packages }}} by default
+Note: If installing on Mac OS X 10.6 running {{{ easy_install http://svn.edgewall.org/repos/trac/trunk }}} will install into {{{ /usr/local }}} and {{{ /Library/Python/2.6/site-packages }}} by default.
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 ==
+== Creating a Project Environment
A [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 [TracIni configuration file], and various other files and directories.
A new environment is created using [wiki:TracAdmin trac-admin]:
-{{{
+{{{#!sh
$ trac-admin /path/to/myproject initenv
}}}
@@ -221,15 +230,19 @@ $ trac-admin /path/to/myproject initenv
Using the default database connection string in particular will always work as long as you have SQLite installed.
For the other [DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point.
-Since 0.12, Trac doesn't ask for a [TracEnvironment#SourceCodeRepository source code repository] anymore when creating an environment. Repositories can be [TracRepositoryAdmin added] afterward, or the version control support can be disabled completely if you don't need it.
+Since 0.12, Trac doesn't ask for a [TracEnvironment#SourceCodeRepository source code repository] anymore when creating an environment. Repositories can be [TracRepositoryAdmin added] afterwards, and support for specific version control systems is disabled by default.
Also note that the values you specify here can be changed later by directly editing the [TracIni conf/trac.ini] configuration file.
+When selecting the location of your environment, make sure that the filesystem on which the environment directory resides supports sub-second timestamps (i.e. **not** `ext2` or `ext3` on Linux), as the modification time of the `conf/trac.ini` file will be monitored to decide whether an environment restart is needed or not. A too coarse-grained timestamp resolution may result in inconsistencies in Trac < 1.0.2 (though the best advice is to opt for a platform with sub-second timestamp resolution when possible regardless of the version of Trac you are running).
+
Finally, make sure the user account under which the web front-end runs will have '''write permissions''' to the environment directory and all the files inside. This will be the case if you run `trac-admin ... initenv` as this user. If not, you should set the correct user afterwards. For example on Linux, with the web server running as user `apache` and group `apache`, enter:
-{{{
-# chown -R apache.apache /path/to/myproject
+{{{#!sh
+$ chown -R apache.apache /path/to/myproject
}}}
+The actual username and groupname of the apache server may not be exactly `apache`, and are specified in the Apache configuration file by the directives `User` and `Group` (if Apache `httpd` is what you use).
+
{{{#!div class=important
'''Warning:''' Please only use ASCII-characters for account name and project path, unicode characters are not supported there.
}}}
@@ -237,19 +250,33 @@ Finally, make sure the user account unde
== Deploying Trac
-=== Running the Standalone Server ===
+=== 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]:
-{{{
+{{{#!sh
$ 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:
-{{{
+{{{#!sh
$ tracd -s --port 8000 /path/to/myproject
}}}
-=== Running Trac on a Web Server ===
+{{{#!div style="border: 1pt dotted; margin: 1em"
+**Setuptools Warning:** If the version of your setuptools is in the range 5.4 through 5.6, the environment variable `PKG_RESOURCES_CACHE_ZIP_MANIFESTS` must be set in order to avoid significant performance degradation. The environment variable can be set system-wide, or for just the user that runs the `tracd` process. There are several ways to accomplish this in addition to what is discussed here, and depending on the distribution of your OS.
+
+To be effective system-wide a shell script with the `export` statement may be added to `/etc/profile.d`. To be effective for a user session the `export` statement may be added to `~/.profile`.
+{{{#!sh
+export PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1
+}}}
+
+Alternatively, the variable can be set in the shell before executing `tracd`:
+{{{#!sh
+$ PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1 tracd --port 8000 /path/to/myproject
+}}}
+}}}
+
+=== Running Trac on a Web Server
Trac provides various options for connecting to a "real" web server:
- [wiki:TracFastCgi FastCGI]
@@ -259,20 +286,21 @@ Trac provides various options for connec
Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. Other deployment scenarios are possible: [trac:TracNginxRecipe nginx], [http://projects.unbit.it/uwsgi/wiki/Example#Traconapacheinasub-uri uwsgi], [trac:TracOnWindowsIisIsapi Isapi-wsgi] etc.
-==== Generating the Trac cgi-bin directory ==== #cgi-bin
+==== Generating the Trac cgi-bin directory #cgi-bin
In order for Trac to function properly with FastCGI you need to have a `trac.fcgi` file and for mod_wsgi a `trac.wsgi` file. These are Python scripts which load the appropriate Python code. They can be generated using the `deploy` option of [wiki:TracAdmin trac-admin].
There is, however, a bit of a chicken-and-egg problem. The [wiki:TracAdmin trac-admin] command requires an existing environment to function, but complains if the deploy directory already exists. This is a problem, because environments are often stored in a subdirectory of the deploy. The solution is to do something like this:
-{{{
+{{{#!sh
mkdir -p /usr/share/trac/projects/my-project
trac-admin /usr/share/trac/projects/my-project initenv
trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy
mv /tmp/deploy/* /usr/share/trac
}}}
+Don't forget to check that the web server has the execution right on scripts in the `/usr/share/trac/cgi-bin` directory.
-==== Mapping Static Resources ====
+==== Mapping Static Resources
Out of the box, Trac will pass static resources such as style sheets or images through itself. For anything but a tracd only based deployment, this is far from optimal as the web server could be set up to directly serve those static resources (for CGI setup, this is '''highly undesirable''' and will cause abysmal performance).
@@ -288,15 +316,15 @@ The target `<directory>` will then conta
- `common/` - the static resources of Trac itself
- `<plugins>/` - one directory for each resource directory managed by the plugins enabled for this environment
-===== Example: Apache and `ScriptAlias` ===== #ScriptAlias-example
+===== Example: Apache and `ScriptAlias` #ScriptAlias-example
Assuming the deployment has been done this way:
-{{{
+{{{#!sh
$ trac-admin /var/trac/env deploy /path/to/trac/htdocs/common
}}}
Add the following snippet to Apache configuration ''before'' the `ScriptAlias` or `WSGIScriptAlias` (which map all the other requests to the Trac application), changing paths to match your deployment:
-{{{
+{{{#!apache
Alias /trac/chrome/common /path/to/trac/htdocs/common
Alias /trac/chrome/site /path/to/trac/htdocs/site
@@ -307,7 +335,7 @@ Alias /trac/chrome/site /path/to/trac/ht
}}}
If using mod_python, you might want to add this too (otherwise, the alias will be ignored):
-{{{
+{{{#!apache
<Location "/trac/chrome/common/">
SetHandler None
</Location>
@@ -316,7 +344,7 @@ If using mod_python, you might want to a
Note that we mapped `/trac` part of the URL to the `trac.*cgi` script, and the path `/trac/chrome/common` is the path you have to append to that location to intercept requests to the static resources.
Similarly, if you have static resources in a project's `htdocs` directory (which is referenced by `/trac/chrome/site` URL in themes), you can configure Apache to serve those resources (again, put this ''before'' the `ScriptAlias` or `WSGIScriptAlias` for the .*cgi scripts, and adjust names and locations to match your installation):
-{{{
+{{{#!apache
Alias /trac/chrome/site /path/to/projectenv/htdocs
<Directory "/path/to/projectenv/htdocs">
@@ -326,25 +354,25 @@ Alias /trac/chrome/site /path/to/project
}}}
Alternatively to aliasing `/trac/chrome/common`, you can tell Trac to generate direct links for those static resources (and only those), using the [[wiki:TracIni#trac-section| [trac] htdocs_location]] configuration setting:
-{{{
+{{{#!ini
[trac]
htdocs_location = http://static.example.org/trac-common/
}}}
Note that this makes it easy to have a dedicated domain serve those static resources (preferentially [http://code.google.com/speed/page-speed/docs/request.html#ServeFromCookielessDomain cookie-less]).
Of course, you still need to make the Trac `htdocs/common` 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:
-{{{
+{{{#!sh
$ ln -s /path/to/trac/htdocs/common /var/www/static.example.org/trac-common
}}}
-==== Setting up the Plugin Cache ====
+==== 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 on how to set environment variables.
+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 on how to set environment variables.
-== Configuring Authentication ==
+== Configuring Authentication
-Trac uses HTTP authentication. You'll need to configure your webserver to request authentication when the `.../login` URL is hit (the virtual path of the "login" button). Trac will automatically pick the REMOTE_USER variable up after you provide your credentials. Therefore, all user management goes through your web server configuration. Please consult the documentation of your web server for more info.
+Trac uses HTTP authentication. You'll need to configure your webserver to request authentication when the `.../login` URL is hit (the virtual path of the "login" button). Trac will automatically pick the `REMOTE_USER` variable up after you provide your credentials. Therefore, all user management goes through your web server configuration. Please consult the documentation of your web server for more info.
The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac.
@@ -353,28 +381,46 @@ Please refer to one of the following sec
* [wiki:TracModWSGI#ConfiguringAuthentication TracModWSGI#ConfiguringAuthentication] if you use the Apache web server, with any of its front end: `mod_wsgi` of course, but the same instructions applies also for `mod_python`, `mod_fcgi` or `mod_fastcgi`.
* TracFastCgi if you're using another web server with FCGI support (Cherokee, Lighttpd, !LiteSpeed, nginx)
+The following document also constains some useful information for beginners: [trac:TracAuthenticationIntroduction].
+
== Granting admin rights to the admin user
Grant admin rights to user admin:
-{{{
+{{{#!sh
$ trac-admin /path/to/myproject permission add admin TRAC_ADMIN
}}}
-This user will have an "Admin" entry menu that will allow you to admin your trac project.
+This user will have an "Admin" entry menu that will allow you to administrate your Trac project.
== Finishing the install
-=== Automatic reference to the SVN changesets in Trac tickets ===
+=== Enable version control components
+
+Support for version control systems is provided by optional components in Trac and the components are disabled by default //(since 1.0)//. Subversion and Git must be explicitly enabled if you wish to use them. See TracRepositoryAdmin for more details.
+
+The components can be enabled by adding the following to the `[components]` section of your [TracIni#components-section trac.ini], or enabling the components in the "Plugins" admin panel.
+
+{{{#!ini
+tracopt.versioncontrol.svn.* = enabled
+}}}
+
+{{{#!ini
+tracopt.versioncontrol.git.* = enabled
+}}}
+
+After enabling the components, repositories can be configured through the "Repositories" admin panel or by editing [TracIni#repositories-section trac.ini].
+
+=== 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 changes 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''
This functionality requires a post-commit hook to be installed as described in [wiki:TracRepositoryAdmin#ExplicitSync TracRepositoryAdmin], and enabling the optional commit updater components by adding the following line to the `[components]` section of your [wiki:TracIni#components-section trac.ini], or enabling the components in the "Plugins" admin panel.
-{{{
+{{{#!ini
tracopt.ticket.commit_updater.* = enabled
}}}
For more information, see the documentation of the `CommitTicketUpdater` component in the "Plugins" admin panel.
-=== Using Trac ===
+=== Using Trac
Once you have your Trac site up and running, you should be able to create tickets, view the timeline, browse your version control repository if configured, etc.
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracInterfaceCustomization
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracInterfaceCustomization?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracInterfaceCustomization (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracInterfaceCustomization Fri Nov 14 11:06:23 2014
@@ -33,7 +33,7 @@ Icons should be a 32x32 image in `.gif`
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:
+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]
@@ -98,7 +98,7 @@ header and footer. Save the following co
</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 a CSS file placed into environment's `htdocs/` directory. In a similar fashion `${chrome.htdocs_location}` is used to specify the common `htdocs/` directory belonging to a Trac installation. That latter location can however be overriden using the [[TracIni#trac-config|[trac] htdocs_location]] configuration setting.
+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 a CSS file placed into environment's `htdocs/` directory. In a similar fashion `${chrome.htdocs_location}` is used to specify the common `htdocs/` directory belonging to a Trac installation. That latter location can however be overriden using the [[TracIni#trac-section|[trac] htdocs_location]] configuration setting.
`site.html` is one file to contain all your modifications. It usually works using the `py:match` directive (element or 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.
@@ -135,7 +135,7 @@ If the environment is upgraded from 0.10
</form>
}}}
-Also note that the `site.html` (despite its name) can be put in a common templates directory - see the [[TracIni#inherit-section|[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.
+Also note that the `site.html` (despite its name) can be put in a shared templates directory - see the [[TracIni#inherit-section|[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
@@ -220,4 +220,4 @@ Trac resolves requests for a template by
Trac caches templates in memory by default to improve performance. To apply a template you need to restart the server.
----
-See also TracGuide, TracIni
+See also TracGuide, TracIni
\ No newline at end of file
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracLinks
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracLinks?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracLinks (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracLinks Fri Nov 14 11:06:23 2014
@@ -27,7 +27,7 @@ and any other text fields explicitly mar
Reports :: `{1}` or `report:1`
Milestones :: `milestone:1.0`
Attachment :: `attachment:example.tgz` (for current page attachment), `attachment:attachment.1073.diff:ticket:944` (absolute path)
- Changesets :: `r1`, `[1]`, `changeset:1` or (restricted) `[1/trunk]`, `changeset:1/trunk`
+ Changesets :: `r1`, `[1]`, `changeset:1` or (restricted) `[1/trunk]`, `changeset:1/trunk`, `[1/repository]`
Revision log :: `r1:3`, `[1:3]` or `log:@1:3`, `log:trunk@1:3`, `[2:5/trunk]`
Diffs :: `diff:@1:3`, `diff:plugins/0.12/mercurial-plugin@9128:9953`,
`diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default`
@@ -42,7 +42,7 @@ and any other text fields explicitly mar
Reports :: {1} or report:1
Milestones :: milestone:1.0
Attachment :: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944 (absolute path)
- Changesets :: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk
+ Changesets :: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk, [1/repository]
Revision log :: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
Diffs :: diff:@1:3, diff:plugins/0.12/mercurial-plugin@9128:9953,
diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default
@@ -315,13 +315,15 @@ Example:
=== 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.
+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 if you don't want to compute the UTC time, you can specify a local time followed by your timezone offset relative to UTC.
Examples:
- `timeline:2008-01-29`
- `timeline:2008-01-29T15:48`
- `timeline:2008-01-29T15:48Z`
- `timeline:2008-01-29T16:48+01`
+ - `timeline:2008-01-29T16:48+0100`
+ - `timeline:2008-01-29T16:48+01:00`
''(since Trac 0.11)''
@@ -349,9 +351,9 @@ If the revision is specified, one can ev
- `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)''
+Finally, one can also highlight an arbitrary set of lines ''(since 0.11)'':
+ - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103, and target line 99
+ - or without version number (the `@` is still needed): `source:/some/file@:10-20,100,103#L99`. Version can be omitted when the path is pointing to a source file that will no longer change (like `source:/tags/...`), otherwise it's better to specify which lines of //which version// of the file you're talking about
Note that in presence of multiple repositories, the name of the repository is simply integrated in the path you specify for `source:` (e.g. `source:reponame/trunk/README`). ''(since 0.12)''
@@ -386,4 +388,4 @@ In the presence of multiple repositories
----
See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki
-
+
\ No newline at end of file
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracModWSGI
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracModWSGI?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracModWSGI (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracModWSGI Fri Nov 14 11:06:23 2014
@@ -1,7 +1,7 @@
= Trac and mod_wsgi =
-[http://code.google.com/p/modwsgi/ mod_wsgi] is an Apache module for running WSGI-compatible Python applications directly on top of the Apache webserver. The mod_wsgi adapter is written completely in C and provides very good performances.
+[http://code.google.com/p/modwsgi/ mod_wsgi] is an Apache module for running WSGI-compatible Python applications directly on top of the Apache webserver. The mod_wsgi adapter is written completely in C and provides very good performance.
[[PageOutline(2-3,Overview,inline)]]
@@ -24,6 +24,16 @@ application = trac.web.main.dispatch_req
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.
+On Windows:
+ - If run under the user's session, the Python Egg cache can be found in `%AppData%\Roaming`, for example:
+{{{#!python
+os.environ['PYTHON_EGG_CACHE'] = r'C:\Users\Administrator\AppData\Roaming\Python-Eggs'
+}}}
+ - If run under a Window service, you should create a directory for Python Egg cache.
+{{{#!python
+os.environ['PYTHON_EGG_CACHE'] = r'C:\Trac-Python-Eggs'
+}}}
+
=== A more elaborate script
If you're using multiple `.wsgi` files (for example one per Trac environment) you must ''not'' use `os.environ['TRAC_ENV']` to set the path to the Trac environment. Using this method may lead to Trac delivering the content of another Trac environment, as the variable may be filled with the path of a previously viewed Trac environment.
@@ -72,7 +82,7 @@ WSGIScriptAlias /trac /usr/local/trac/my
Here, the script is in a subdirectory of the Trac environment.
-If you followed the directions [http://trac.edgewall.org/wiki/TracInstall#cgi-bin Generating the Trac cgi-bin directory], your Apache configuration file should look like following:
+If you followed the directions [TracInstall#cgi-bin Generating the Trac cgi-bin directory], your Apache configuration file should look like following:
{{{
WSGIScriptAlias /trac /usr/share/trac/cgi-bin/trac.wsgi
@@ -171,6 +181,8 @@ The "trac" parameter above is the "realm
For multiple environments, you can use the same `LocationMatch` as described with the previous method.
+'''Note: `Location` cannot be used inside .htaccess files, but must instead live within the main httpd.conf file. If you are on a shared server, you therefore will not be able to provide this level of granularity. '''
+
Don't forget to activate the mod_auth_digest. For example, on a Debian 4.0r1 (etch) system:
{{{
LoadModule auth_digest_module /usr/lib/apache2/modules/mod_auth_digest.so
@@ -307,7 +319,7 @@ This will generally be matched with an A
Require valid-user
</Location>
}}}
-Note that '''authFile''' need not exist. See the !HttpAuthStore link above for examples where multiple Trac projects are hosted on a server.
+Note that '''authFile''' need not exist (unless you are using Account Manager older than 0.4). See the !HttpAuthStore link above for examples where multiple Trac projects are hosted on a server.
=== Example: Apache/mod_wsgi with Basic Authentication, Trac being at the root of a virtual host
@@ -387,14 +399,14 @@ A somewhat brutal workaround is to disab
But it's not necessary to edit the source of Trac, the following lines in `trac.wsgi` will also work:
-{{{
+{{{#!python
import trac.db.postgres_backend
trac.db.postgres_backend.PostgreSQLConnection.poolable = False
}}}
or
-{{{
+{{{#!python
import trac.db.mysql_backend
trac.db.mysql_backend.MySQLConnection.poolable = False
}}}
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracNotification
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracNotification?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracNotification (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracNotification Fri Nov 14 11:06:23 2014
@@ -27,41 +27,7 @@ When using apache and mod_kerb for authe
=== 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_from_author`''': (''since 1.0'') Use the author of a change (the reporter of a new ticket, or the author of a comment) as the `From:` header value in notification e-mails (default: false). If the author hasn't set an e-mail address, `smtp_from` and `smtp_from_name` are used instead.
- * '''`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.
- * '''`ignore_domains`''': Comma-separated list of domains that should not be considered part of email addresses (for usernames with Kerberos domains).
- * '''`mime_encoding`''': (''since 0.10'') This option allows selecting the MIME encoding scheme. Supported values:
- * `none`: default value, uses 7bit encoding if the text is plain ASCII, or 8bit otherwise.
- * `base64`: 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) if 8bit encoding cannot be used.
- * '''`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.
- * '''`email_sender`''': (''since 0.12'') Name of the component implementing `IEmailSender`. This component is used by the notification system to send emails. Trac currently provides the following components:
- * `SmtpEmailSender`: connects to an SMTP server (default).
- * `SendmailEmailSender`: runs a `sendmail`-compatible executable.
-
-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.
-
-The following option is specific to email delivery through a `sendmail`-compatible executable.
- * '''`sendmail_path`''': (''since 0.12'') Path to the sendmail executable. The sendmail program must accept the `-i` and `-f` options.
+[[TracIni(notification)]]
=== Example Configuration (SMTP) ===
{{{
@@ -98,7 +64,7 @@ The following variables are available in
=== Customizing the e-mail content ===
-The notification e-mail content is generated based on `ticket_notify_email.txt` in `trac/templates`. You can add your own version of this template by adding a `ticket_notify_email.txt` to the templates directory of your environment. The default looks like this:
+The notification e-mail content is generated based on `ticket_notify_email.txt` in `trac/ticket/templates`. You can add your own version of this template by adding a `ticket_notify_email.txt` to the templates directory of your environment. The default looks like this:
{{{
$ticket_body_hdr
@@ -245,17 +211,12 @@ 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.
+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 [trac:comment:2:ticket:7107 #7107] for details.
-== Filtering notifications for one's own changes ==
+== Filtering notifications for one's own changes and comments ==
In Gmail, use the filter:
{{{
-from:(<smtp_from>) (("Reporter: <username>" -Changes) OR "Changes (by <username>)")
-}}}
-
-For Trac .10, use the filter:
-{{{
from:(<smtp_from>) (("Reporter: <username>" -Changes -Comment) OR "Changes (by <username>)" OR "Comment (by <username>)")
}}}
@@ -264,11 +225,8 @@ 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
+http://trac-hacks.org/wiki/NeverNotifyUpdaterPlugin, or vote for [trac:#2247] to be fixed.
== Troubleshooting ==
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracPermissions
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracPermissions?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracPermissions (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracPermissions Fri Nov 14 11:06:23 2014
@@ -13,7 +13,7 @@ In addition to these privileges, users c
== Graphical Admin Tab ==
''This feature is new in version 0.11.''
-To access this tab, a user must have one of the following permissions: `TRAC_ADMIN`, `PERMISSION_ADMIN`, `PERMISSION_ADD`, `PERMISSION_REMOVE`. The permissions can granted using the `trac-admin` command (more on `trac-admin` below):
+To access this tab, a user must have one of the following permissions: `TRAC_ADMIN`, `PERMISSION_ADMIN`, `PERMISSION_GRANT`, `PERMISSION_REVOKE`. The permissions can be granted using the `trac-admin` command (more on `trac-admin` below):
{{{
$ trac-admin /path/to/projenv permission add bob TRAC_ADMIN
}}}
@@ -26,6 +26,8 @@ Then, the user `bob` will be able to see
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.
+From the graphical admin tab, users with `PERMISSION_GRANT` will only be allowed to grant permissions that they possess, and users with `PERMISSION_REVOKE` will only be allowed to revoke permissions that they possess. For example, a user cannot grant `MILESTONE_ADMIN` unless they have `PERMISSION_GRANT` and `MILESTONE_ADMIN`, and they cannot revoke `MILESTONE_ADMIN` unless they have `PERMISSION_REVOKE` and `MILESTONE_ADMIN`. `PERMISSION_ADMIN` just grants the user both `PERMISSION_GRANT` and `PERMISSION_REVOKE`, and users with `TRAC_ADMIN` can grant or revoke any permission.
+
== 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.
@@ -97,7 +99,7 @@ Attention: the "view tickets" button app
== Creating New Privileges ==
-To create custom permissions, for example to be used in a custom workflow, enable the optional [trac:ExtraPermissionsProvider tracopt.perm.config_perm_provider.ExtraPermissionsProvider] component in the "Plugins" admin panel, and add the desired permissions to the `[extra-permissions]` section in your [wiki:TracIni#extra-permissions-section trac.ini]. For more information, please refer to the documentation of the component in the admin panel.
+To create custom permissions, for example to be used in a custom workflow, enable the optional [trac:ExtraPermissionsProvider tracopt.perm.config_perm_provider.ExtraPermissionsProvider] component in the "Plugins" admin panel, and add the desired permissions to the `[extra-permissions]` section in your [wiki:TracIni#extra-permissions-section trac.ini]. For more information, please refer to the documentation on the [wiki:TracIni#extra-permissions-section TracIni] page after enabling the component.
== Granting Privileges ==
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracPlugins
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracPlugins?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracPlugins (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracPlugins Fri Nov 14 11:06:23 2014
@@ -168,6 +168,7 @@ If you install a plugin globally (i.e.,
* ...you actually added the necessary line(s) to the `[components]` section.
* ...the package/module names are correct.
* ...the value is "enabled", not "enable" or "Enable".
+ * ...the section name is "components", not "component".
=== Check the permissions on the .egg file ===
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracQuery
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracQuery?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracQuery (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracQuery Fri Nov 14 11:06:23 2014
@@ -83,7 +83,7 @@ A more compact representation without th
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, use the ``count`` parameter.
+Finally, if you wish to receive only the number of defects that match the query, use the `count` parameter.
{{{
[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracReports
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracReports?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracReports (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracReports Fri Nov 14 11:06:23 2014
@@ -135,7 +135,6 @@ Example:
http://trac.edgewall.org/reports/14?PRIORITY=high&SEVERITY=critical
}}}
-Dynamic variables can also be used in the report title and description (since 1.1.1).
=== !Special/Constant Variables ===
There is one dynamic variable whose value is set automatically (the URL does not have to be changed) to allow practical reports.
@@ -163,6 +162,7 @@ final report.
* '''ticket''' â Ticket ID number. Becomes a hyperlink to that ticket.
* '''id''' â same as '''ticket''' above when '''realm''' is not set
* '''realm''' â together with '''id''', can be used to create links to other resources than tickets (e.g. a realm of ''wiki'' and an ''id'' to a page name will create a link to that wiki page)
+ - for some kind of resources, it may be necessary to specify their ''parent'' resources (e.g. for ''changeset'', which ''repos'') and this can be achieved using the '''parent_realm''' and '''parent_id''' columns
* '''created, modified, date, time''' â Format cell as a date and/or time.
* '''description''' â Ticket description field, parsed through the wiki engine.
Modified: bloodhound/vendor/trac/current/trac/wiki/default-pages/TracRepositoryAdmin
URL: http://svn.apache.org/viewvc/bloodhound/vendor/trac/current/trac/wiki/default-pages/TracRepositoryAdmin?rev=1639602&r1=1639601&r2=1639602&view=diff
==============================================================================
--- bloodhound/vendor/trac/current/trac/wiki/default-pages/TracRepositoryAdmin (original)
+++ bloodhound/vendor/trac/current/trac/wiki/default-pages/TracRepositoryAdmin Fri Nov 14 11:06:23 2014
@@ -89,7 +89,7 @@ There is also new functionality in the f
Please note that at the time of writing, no initial resynchronization or any hooks are necessary for Mercurial repositories - see [trac:#9485] for more information.
=== Explicit synchronization === #ExplicitSync
-This is the preferred method of repository synchronization. It requires setting the `[trac] repository_sync_per_request` option in [wiki:TracIni#trac-section trac.ini] to an empty value, and adding a call to `trac-admin` in the post-commit hook of each repository. Additionally, if a repository allows changing revision metadata, a call to `trac-admin` must be added to the post-revprop-change hook as well.
+This is the preferred method of repository synchronization. It requires setting the `[trac] repository_sync_per_request` option in [wiki:TracIni#trac-section trac.ini] to an empty value, and adding a call to `trac-admin` in the `post-commit` hook of each repository. Additionally, if a repository allows changing revision metadata, a call to `trac-admin` must be added to the `post-revprop-change` hook as well.
`changeset added <repos> <rev> [...]`::
Notify Trac that one or more changesets have been added to a repository.
@@ -99,7 +99,9 @@ This is the preferred method of reposito
The `<repos>` argument can be either a repository name (use "`(default)`" for the default repository) or the path to the repository.
-Note that you may have to set the environment variable PYTHON_EGG_CACHE to the same value as was used for the web server configuration before calling trac-admin, if you changed it from its default location. See [wiki:TracPlugins Trac Plugins] for more information.
+Note that you may have to set the environment variable `PYTHON_EGG_CACHE` to the same value as was used for the web server configuration before calling `trac-admin`, if you changed it from its default location. See [wiki:TracPlugins Trac Plugins] for more information.
+
+==== Subversion ====
The following examples are complete post-commit and post-revprop-change scripts for Subversion. They should be edited for the specific environment, marked executable (where applicable) and placed in the `hooks` directory of each repository. On Unix (`post-commit`):
{{{#!sh
@@ -107,14 +109,9 @@ The following examples are complete post
export PYTHON_EGG_CACHE="/path/to/dir"
/usr/bin/trac-admin /path/to/env changeset added "$1" "$2"
}}}
-Note: Ubuntu doesn't seem to like /usr/bin/trac-admin, so just use:
-{{{#!sh
-#!/bin/sh
-export PYTHON_EGG_CACHE="/path/to/dir"
-trac-admin /path/to/env/ changeset added "$1" "$2"
-}}}
+Note: Check with `whereis trac-admin`, whether `trac-admin` is really installed under `/usr/bin/` or maybe under `/usr/local/bin/` and adapt the path.
On Windows (`post-commit.cmd`):
-{{{#!application/x-dos-batch
+{{{#!bat
@C:\Python26\Scripts\trac-admin.exe C:\path\to\env changeset added "%1" "%2"
}}}
@@ -125,7 +122,7 @@ export PYTHON_EGG_CACHE="/path/to/dir"
/usr/bin/trac-admin /path/to/env changeset modified "$1" "$2"
}}}
On Windows (`post-revprop-change.cmd`):
-{{{#!application/x-dos-batch
+{{{#!bat
@C:\Python26\Scripts\trac-admin.exe C:\path\to\env changeset modified "%1" "%2"
}}}
@@ -135,12 +132,30 @@ Note that calling `trac-admin` in your S
See the [http://svnbook.red-bean.com/en/1.5/svn.reposadmin.create.html#svn.reposadmin.create.hooks section about hooks] in the Subversion book for more information. Other repository types will require different hook setups.
-Git hooks can be used in the same way for explicit syncing of git repositories. Add the following to `.git/hooks/post-commit`:
+==== Git ====
+
+Git hooks can be used in the same way for explicit syncing of Git repositories. If your git repository is one that gets committed to directly on the machine that hosts trac, add the following to the `hooks/post-receive` file in your git repo (note: this will do nothing if you only update the repo by pushing to it):
{{{#!sh
-REV=$(git rev-parse HEAD)
-trac-admin /path/to/env changeset added <my-repository> $REV
+#!/bin/sh
+REV=$(git rev-parse HEAD)
+trac-admin /path/to/env changeset added <repos> $REV
}}}
+Alternately, if your repository is one that only gets pushed to, add the following to the `hooks/post-receive` file in the repo:
+{{{#!sh
+#!/bin/sh
+while read oldrev newrev refname; do
+ git rev-list --reverse $newrev ^$oldrev | \
+ while read rev; do
+ trac-admin /path/to/env changeset added <repos> $rev
+ done
+done
+}}}
+
+The `<repos>` argument can be either a repository name (use "`(default)`" for the default repository) or the path to the repository.
+
+==== Mercurial ====
+
For Mercurial, add the following entries to the `.hgrc` file of each repository accessed by Trac (if [trac:TracMercurial] is installed in a Trac `plugins` directory, download [trac:source:mercurial-plugin/tracext/hg/hooks.py hooks.py] and place it somewhere accessible):
{{{#!ini
[hooks]