Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
litespeed_wiki:other-ext-apps:python-fcgi-django [2015/08/11 16:04] Michael Alegre Corrected Link |
litespeed_wiki:other-ext-apps:python-fcgi-django [2018/09/13 20:38] Michael Alegre |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| You need to create a FastCGI application from LiteSpeed Web Server web administration console, you can have the FastCGI application started manually, or have it managed by LSWS. | You need to create a FastCGI application from LiteSpeed Web Server web administration console, you can have the FastCGI application started manually, or have it managed by LSWS. | ||
| - | * If you want to start it manually, just create a remote FastCGI application by setting "Auto Start" to "false", and the follow Django documentation. | + | * If you want to start it manually, just create a remote FastCGI application by setting **Start By Server** to ''No'', and the follow Django documentation. |
| * If you want LSWS to manage the FCGI instances directly, you can try the following in the FastCGI external application configuration: | * If you want LSWS to manage the FCGI instances directly, you can try the following in the FastCGI external application configuration: | ||
| MaxConn: 20 (<50 is OK, flup support upto 50 connections by default) | MaxConn: 20 (<50 is OK, flup support upto 50 connections by default) | ||
| - | Auto Start: true | + | Start By Server: Yes |
| Command: path_to_manage.py runfcgi **daemonize=false** (method could be threaded or prefork) | Command: path_to_manage.py runfcgi **daemonize=false** (method could be threaded or prefork) | ||
| Intance: 1 | Intance: 1 | ||