Edgewall Software
Home
Trac
Trac Hacks
Genshi
Babel
Bitten
Home
Download
Documentation
Mailing Lists
License
FAQ
Search:
Login
Preferences
Help/Guide
About Trac
Wiki
Timeline
Roadmap
Browse Source
View Tickets
New Ticket
Search
Context Navigation
-1
Start Page
Index
History
Editing TracDev/TracURLs
Adjust edit area height:
8
12
16
20
24
28
32
36
40
Edit side-by-side
Trac has some ''unusual'' or better said ''special'' conventions about default URL paths (or URL endpoints). These are specified relative to base Trac URL. * [/chrome /chrome] - the handler for this URL just serves files that are placed in `htdocs` folder of [TracEnvironment Trac environment]. [[BR]] [[BR]] These files are usually ''images'', ''.css'' and ''.js'' that are called ''static resources'', because they don't require any server-side processing and can be served as-is. In fact to avoid firing [TracDev/RequestHandling Trac request handling] many people prefer setups when static resources are [TracCgi#MappingStaticResources served by web server] directly. * [/chrome/site /chrome/site] - using this URL Trac accesses static resources for TracInterfaceCustomization that were uploaded to [TracEnvironment environment's] ''htdocs/'' directory * [/chrome/common /chrome/common] - with this URL Trac accesses static resources used by default Trac scheme - these are usually found in ''htdocs/'' subdirectory in Trac installation location * /chrome/<pluginname> - plugins may also have static resources that can be accessed using Trac chrome handler All static resources can be exported with '''trac-admin deploy''' command to serve them independently. The process is described in detail on TracCgi#MappingStaticResources page. Just do not forget to re-export them after installing new plugins or upgrading Trac.
Note:
See
WikiFormatting
and
TracWiki
for help on editing wiki content.
Change information
Your email or username:
E-mail address and name can be saved in the
Preferences
Comment about this change (optional):
Note:
See
TracWiki
for help on using the wiki.