Project

General

Profile

Wt Deployment » History » Version 13

Sean Dacquis, 12/27/2013 03:19 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 6 Richel Bilderbeek
The FastCGI configuration is highly dependent on the web server.
10 1 Koen Deforche
11 9 Peter Mortensen
* [[Fastcgi on apache|FastCGI on Apache]]
12
* [[Fastcgi on lighttpd|FastCGI on lighttpd]]
13
* [[Fastcgi on nginx|FastCGI on nginx]]
14
* [[Litespeed|Litespeed Web Server]]
15 1 Koen Deforche
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
* [[Using HAProxy as a reverse proxy]]
25 6 Richel Bilderbeek
26
h2. External links
27
28
* http://richelbilderbeek.nl/CppWtDeploy.htm: Richel Bilderbeek's page about Wt deployment
29 13 Sean Dacquis
30
31
32
http://depuyhiprecallnewscenter.wordpress.com/
33
http://www.nexopia.com/users/depuyhiprecall/
34
http://haleyhiprecall.livejournal.com/