Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
litespeed_wiki:other-ext-apps:python-fcgi-django [2015/07/29 14:55]
Michael Alegre created
litespeed_wiki:other-ext-apps:python-fcgi-django [2018/09/13 20:38] (current)
Michael Alegre
Line 1: Line 1:
 ====== How to deploy Django project with FastCGI ====== ====== How to deploy Django project with FastCGI ======
-LiteSpeed Web Server can be used to host Django project via FastCGI, for basic information please read "[[http://www.djangoproject.com/​documentation/​fastcgi/​|How to use Django with FastCGI]]"​+LiteSpeed Web Server can be used to host Django project via FastCGI, for basic information please read "[[https://docs.djangoproject.com/​en/​1.8/​howto/​deployment/​fastcgi/​|How to use Django with FastCGI]]"​
  
 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 ServerYes
   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
  • Admin
  • Last modified: 2015/07/29 14:55
  • by Michael Alegre