| 102 | |
| 103 | == Tips == |
| 104 | |
| 105 | === Serving static content === |
| 106 | |
| 107 | If `tracd` is the only webserver used for the project, |
| 108 | it can also be used to distribute static content |
| 109 | (tarballs, Doxygen documentation, etc.) |
| 110 | |
| 111 | This static content should be put in the `$TRAC_ENV/htdocs` folder, |
| 112 | and is accessed by URLs like `<project_URL>/chrome/site/...`. |
| 113 | |
| 114 | Example: given a `$TRAC_ENV/htdocs/software-0.1.tar.gz` file, |
| 115 | the corresponding relative URL would be `/<project_name>/chrome/site/software-0.1.tar.gz`, |
| 116 | which in turn can be written using the relative link syntax |
| 117 | in the Wiki: `[/<project_name>/chrome/site/software-0.1.tar.gz]` |
| 118 | |
| 119 | The development version of Trac supports a new `htdocs:` TracLinks |
| 120 | syntax for the above. With this, the example link above can be written simply |
| 121 | `htdocs:software-0.1.tar.gz`. |
| 122 | |