Changes between Version 1 and Version 2 of InterTrac
- Timestamp:
- Nov 1, 2019, 11:11:25 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
InterTrac
v1 v2 1 = InterTrac Links =1 = InterTrac Links 2 2 3 Trac supports a convenient way to refer to resources of other Trac servers , from within the Wiki markup, since version 0.10.3 Trac supports a convenient way to refer to resources of other Trac servers using Wiki markup. An !InterTrac link can be seen as a scoped [TracLinks TracLink]. It is used for referring to a Trac resource located in another Trac environment. 4 4 5 == Definitions ==5 == Link Syntax 6 6 7 An InterTrac link can be seen as a scoped TracLinks. 8 It is used for referring to a Trac resource 9 (Wiki page, changeset, ticket, ...) located in another 10 Trac environment. 11 12 == List of Active InterTrac Prefixes == 13 14 [[InterTrac]] 15 16 == Link Syntax == 17 18 Simply use the name of the other Trac environment as a prefix, 19 followed by a colon, ending with the resource located in the other environment. 7 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: 20 8 21 9 {{{ … … 23 11 }}} 24 12 25 The other resource is specified using a regular TracLinks, of any flavor.13 The other resource is specified using a regular !TracLink, of any flavor. 26 14 27 That target environment name is either the real name of the 28 environment, or an alias for it. 29 The aliases are defined in `trac.ini` (see below). 15 That target environment name is either the real name of the environment or an alias. 16 The aliases are defined in the `trac.ini` file, see below. 30 17 The prefix is case insensitive. 31 18 32 For convenience, there's also some alternative short-hand form, 33 where one can use an alias as an immediate prefix 34 for the identifier of a ticket, changeset or report: 35 (e.g. `#T234`, `[T1508]`, `[trac 1508]`, ...) 19 If the InterTrac link is enclosed in square brackets, like `[th:WikiExtrasPlugin]`, the InterTrac prefix is removed in the displayed link like a normal link resolver would be. For example, the above would be displayed as `WikiExtrasPlugin`. 36 20 37 == Examples == 21 For convenience, there is also an alternate short-hand form, where an alias can be used as an immediate prefix for the identifier of a ticket, changeset or report, eg `#T234`, `[T1508]`, `[trac 1508]`. 38 22 39 {{{ 40 #!comment 41 Besides the other environments run by the same server process 42 (called ''sibling'' environments), which are automatically detected, 43 Support for sibling environments has been disabled. 44 See http://thread.gmane.org/gmane.comp.version-control.subversion.trac.devel/157 45 }}} 23 == Examples 46 24 47 It is necessary to setup a configuration for the InterTrac facility. 48 This configuration has to be done in the TracIni file, `[intertrac]` section. 25 The only prefix defined by default is `trac`, which points to trac.edgewall.org. Additional prefixes can be specified in the [TracIni#intertrac-section intertrac] section of TracIni. For example: 49 26 50 Example configuration: 51 {{{ 52 ... 27 {{{#!ini 53 28 [intertrac] 54 29 # -- Example of setting up an alias: … … 56 31 57 32 # -- Link to an external Trac: 58 trac.title = Edgewall's Trac for Trac 59 trac.url = http://projects.edgewall.com/trac 60 trac.compat = false 33 genshi.title = Edgewall's Trac for Genshi 34 genshi.url = http://genshi.edgewall.org 61 35 }}} 62 36 63 37 The `.url` is mandatory and is used for locating the other Trac. 64 This can be a relative URL in case that Trac environment is located 65 on the same server. 38 It can be a relative URL when the Trac environment is located on the same server. 66 39 67 The `.title` information will be used for providing an useful tooltip 68 when moving the cursor over an InterTrac links. 69 70 Finally, the `.compat` option can be used to activate or disable 71 a ''compatbility'' mode: 72 * If the targeted Trac is running a version below milestone:0.10 73 (r3526 to be precise), then it doesn't know how to dispatch an InterTrac 74 link, and it's up to the local Trac to prepare the correct link. 75 Not all links will work that way, but the most common do. 76 This is called the compatibility mode, and is `true` by default. 77 * If you know that the remote Trac knows how to dispatch InterTrac links, 78 you can explicitely disable this compatibility mode and then ''any'' 79 TracLinks can become an InterTrac link. 40 The `.title` information is used in a tooltip, ie when hovering the cursor over an InterTrac link. 80 41 81 42 Now, given the above configuration, one could create the following links: … … 83 44 * `trac:wiki:InterTrac` trac:wiki:InterTrac 84 45 * `t:wiki:InterTrac` t:wiki:InterTrac 46 * `genshi:InterTrac` genshi:InterTrac 85 47 * Keys are case insensitive: `T:wiki:InterTrac` T:wiki:InterTrac 86 48 * to the ticket #234: 87 49 * `trac:ticket:234` trac:ticket:234 88 50 * `trac:#234` trac:#234 51 * `genshi:#234` genshi:#234 89 52 * `#T234` #T234 90 53 * to the changeset [1912]: 91 54 * `trac:changeset:1912` trac:changeset:1912 92 55 * `[T1912]` [T1912] 93 * to the log range [3300:3330]: '''(Note: the following ones need `trac.compat=false`)'''56 * to the log range [3300:3330]: 94 57 * `trac:log:@3300:3330` trac:log:@3300:3330 95 * `[trac 3300:3330]` [trac 3300:3330] 58 * `[trac 3300:3330]` [trac 3300:3330] 59 * 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]` (note that the ''remote'' Trac has to run Trac >= 0.11 for this to work'') 96 60 97 The generic form `intertrac_prefix:module:id` is translated 98 to the corresponding URL `<remote>/module/id`, shorthand links 99 are specific to some modules (e.g. !#T234 is processed by the 100 ticket module) and for the rest (`intertrac_prefix:something`), 101 we rely on the TracSearch#quickjump facility of the remote Trac. 61 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). For the rest (`intertrac_prefix:something`), we rely on the [TracSearch#quickjump quick jump] facility of the remote Trac. 102 62 103 ---- 104 === Discussion === 63 == List of Active InterTrac Prefixes 105 64 106 I think that the `trac` prefix could even be set as a default in the `[intertrac]` TracIni section. --CB 65 The following InterTrac prefixes are available on this site: 66 67 [[InterTrac]] 107 68 108 69 ----