Changes between Version 434 and Version 435 of TracInstall

Timestamp:

Jun 11, 2017, 3:39:29 PM (7 years ago)

Author:

Ryan J Ollos

Comment:

Tweak markup to avoid problems with ReST export.

TracInstall

@@ -275 +275 @@
  - [wiki:TracModWSGI Apache with mod_wsgi] 
  - [TracModPython Apache with mod_python]
- - //[TracCgi CGI] (should not be used, as the performance is far from optimal)//
+ - [TracCgi CGI] //(should not be used, as the performance is far from optimal)//
 
 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.
@@ -302 +302 @@
 A single `/chrome` alias can used if the static resources are extracted for all plugins. This means that the `deploy` command must be executed after installing or updating a plugin that provides static resources, or after modifying resources in the `$env/htdocs` directory. This is probably appropriate for most installations but may not be what you want if, for example, you wish to upload plugins through the //Plugins// administration page.
 
-The resources are extracted using the [TracAdmin trac-admin]` <environment> deploy` command:
+The resources are extracted using the [TracAdmin trac-admin] `<environment> deploy` command:
 [[TracAdminHelp(deploy)]]
 
@@ -367 +367 @@
 }}}
 
-Another alternative to aliasing `/trac/chrome/common` is having Trac generate direct links for those static resources (and only those), using the [[TracIni#trac-section| [trac] htdocs_location]] configuration setting:
+Another alternative to aliasing `/trac/chrome/common` is having Trac generate direct links for those static resources (and only those), using the [TracIni#trac-section htdocs_location] configuration setting:
 {{{#!ini
 [trac]