Note that you will need to add a new entry to `fastcgi.server` for each separate Trac instance that you wish to run. Alternatively, you may use the `TRAC_ENV_PARENT_DIR` variable instead of `TRAC_ENV` as described above.

85

Note that you will need to add a new entry to `fastcgi.server` for each separate Trac instance that you wish to run. Alternatively, you may use the `TRAC_ENV_PARENT_DIR` variable instead of `TRAC_ENV` as described above,

86

and you may set one of the two in `trac.fcgi` instead of in `lighttpd.conf`

87

using `bin-environment` (as in the section above on Apache configuration).

88

89

For using two projects with lighttpd add the following to your `lighttpd.conf`:

90

{{{

91

fastcgi.server = ("/first" =>

92

("first" =>

93

("socket" => "/tmp/trac-fastcgi-first.sock",

94

"bin-path" => "/path/to/cgi-bin/trac.fcgi",

95

"check-local" => "disable",

96

"bin-environment" =>

97

("TRAC_ENV" => "/path/to/projenv-first")

98

)

99

),

100

"/second" =>

101

("second" =>

102

("socket" => "/tmp/trac-fastcgi-second.sock",

103

"bin-path" => "/path/to/cgi-bin/trac.fcgi",

104

"check-local" => "disable",

105

"bin-environment" =>

106

("TRAC_ENV" => "/path/to/projenv-second")

107

)

108

)

109

)

110

}}}

111

Note that field values are different. If you prefer setting the environment

112

variables in the `.fcgi` scripts, then copy/rename `trac.fcgi`, e.g., to

113

`first.fcgi` and `second.fcgi`, and reference them in the above settings.

114

Note that the above will result in different processes in any event, even

<strong>Note from c00i90wn:</strong> It's very important the order on which server.modules are loaded, if mod_auth is not loaded <strong>BEFORE</strong> mod_fastcgi, then the server will fail to authenticate the user.

120

</p>

121

}}}

122

For authentication you should enable mod_auth in lighttpd.conf 'server.modules', select auth.backend and auth rules:

Other important information like [http://trac.lighttpd.net/trac/wiki/TracInstall this updated TracInstall page], [wiki:TracCgi#MappingStaticResources and this] are useful for non-fastcgi specific installation aspects.

53

236

237

If you use trac-0.9, read [http://lists.edgewall.com/archive/trac/2005-November/005311.html about small bug]

238

54

239

Relaunch lighttpd, and browse to `http://yourhost.example.org/trac` to access Trac.

240

241

Note about running lighttpd with reduced permissions:

242

243

If nothing else helps and trac.fcgi doesn't start with lighttpd settings __server.username = "www-data"__, __server.groupname = "www-data"__, then in the `bin-environment` section set `PYTHON_EGG_CACHE` to the home directory of `www-data` or some other directory accessible to this account for writing.

244

245

246

== Simple LiteSpeed Configuration ==

247

248

The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://www.litespeedtech.com/ LiteSpeed].

249

250

LiteSpeed web server is an event-driven asynchronous Apache replacement designed from the ground-up to be secure, scalable, and operate with minimal resources. LiteSpeed can operate directly from an Apache config file and is targeted for business-critical environments.

251

252

Setup

253

254

1) Please make sure you have first have a working install of a Trac project. Test install with “tracd” first.

255

256

2) Create a Virtual Host for this setup. From now on we will refer to this vhost as TracVhost. For this tutorial we will be assuming that your trac project will be accessible via: