Changes between Version 335 and Version 336 of TracInstall

Timestamp:

Feb 27, 2011, 3:20:32 PM (13 years ago)

Author:

Christian Boos

Comment:

Adding a #DeployingTrac section

TracInstall

@@ -256 +256 @@
 
 
-== Running the Standalone Server ==
+== Deploying Trac
+
+=== 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]:
@@ -268 +270 @@
 }}}
 
-== Running Trac on a Web Server ==
-
-Trac provides various options for connecting to a "real" web server: [wiki:TracCgi CGI], [wiki:TracFastCgi FastCGI], [wiki:TracModWSGI mod_wsgi] and [wiki:TracModPython mod_python]. For decent performance, it is recommended that you use either FastCGI or mod_wsgi.
-
-Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS.
-
-==== Generating the Trac cgi-bin directory ====
+=== Running Trac on a Web Server ===
+
+Trac provides various options for connecting to a "real" web server: 
+ - [wiki:TracFastCgi FastCGI]
+ - [wiki:TracModWSGI mod_wsgi] 
+ - [wiki:TracModPython mod_python] (no longer recommended, as mod_python is not actively maintained anymore)
+ - //[wiki: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], etc.
+
+==== 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].
@@ -295 +301 @@
 There are two primary URL paths for static resources - `/chrome/common` and `/chrome/site`. Plugins can add their own resources usually accessible by `/chrome/plugin` path, so its important to override only known paths and not try to make universal `/chrome` alias for everything.
 
+Note that in order to get those static resources on the filesystem, you need first to extract the relevant Trac resources using the `deploy` command of TracAdmin:
+[[TracAdminHelp(deploy)]]
+
+See the `htdocs` directory within the target `<directory>`.
+
+
 ===== Example: Apache and `ScriptAlias` =====
 
-Add the following snippet to Apache configuration '''before''' the `ScriptAlias` for the CGI script, changing paths to match your deployment:
+Add the following snippet to Apache configuration ''before'' the `ScriptAlias` or `WsgiScriptAlias` (which maps all the other requests to the Trac application), changing paths to match your deployment:
 {{{
 Alias /trac/chrome/common /path/to/trac/htdocs/common
@@ -342 +354 @@
 $ ln -s /path/to/www/trac/htdocs /var/www/yourhost.example.org/trac-htdocs
 }}}
-
-Note that in order to get this `htdocs` directory, you need first to extract the relevant Trac resources using the `deploy` command of TracAdmin:
-[[TracAdminHelp(deploy)]]