Wt Deployment » History » Version 4
Koen Deforche, 11/24/2010 04:29 PM
| 1 | 1 | Koen Deforche | h1. Wt Deployment |
|---|---|---|---|
| 2 | |||
| 3 | This page lists various deployment options. |
||
| 4 | |||
| 5 | 4 | Koen Deforche | Your first choice with respect to deployment is a choice of one of the available connectors: FastCGI, ISAPI or built-in httpd. |
| 6 | 1 | Koen Deforche | |
| 7 | h2. Deployment using FastCGI |
||
| 8 | |||
| 9 | The FastCGI configuration is highly dependent on the web server. |
||
| 10 | |||
| 11 | * [[Fastcgi on apache]] |
||
| 12 | * [[Fastcgi on lighttpd]] |
||
| 13 | * [[Fastcgi on nginx]] |
||
| 14 | * [[Litespeed]] |
||
| 15 | |||
| 16 | h2. Deployment using ISAPI |
||
| 17 | |||
| 18 | * [[ISAPI on Microsoft IIS]] |
||
| 19 | |||
| 20 | 3 | Koen Deforche | h2. Reverse proxy + built-in HTTPD |
| 21 | 1 | Koen Deforche | |
| 22 | While the built-in httpd serves as a standalone deployment option, it is often used in conjunction with a (load-balancing) reverse proxy web server for production. |
||
| 23 | |||
| 24 | 2 | Koen Deforche | * [[Using HAProxy as a reverse proxy]] |