|
Size: 1366
Comment:
|
Size: 1526
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 29: | Line 29: |
| Upstream recommends using `spawn-fcgi(1)`, rather than `fcgiwrap(8)` directly. With it, no configuration is necessary and the server can be started like: | === NGINX === See [[NGINX/FastCGI#Fcgiwrap|here]] for details. However, it should be noted that upstream recommends using `spawn-fcgi(1)`, rather than `fcgiwrap(8)` directly. With it, no configuration is necessary and the server can be started like: |
| Line 34: | Line 40: |
See [[NGINX/FastCGI#Spawn-fcgi|here]] for details. |
Fcgiwrap
fcgiwrap(8) is a simple wrapper script around a FastCGI implementation.
Contents
Installation
Most Linux distributions offer a fcgiwrap package. Consider also installed spawn-fcgi at the same time (see below).
Enable and start fcgiwrap.socket.
Configuration
Usage
NGINX
See here for details.
However, it should be noted that upstream recommends using spawn-fcgi(1), rather than fcgiwrap(8) directly. With it, no configuration is necessary and the server can be started like:
spawn-fcgi -n -u www-data -p 9000 -- /usr/bin/fcgiwrap -f
See here for details.
Path_Info
Upstream has noted that fcgiwrap(8) was written before NGINX offered fastcgi_split_path_info.
"PATH_INFO passed from the web server is ignored and instead is parsed out of SCRIPT_FILENAME (or DOCUMENT_ROOT + SCRIPT_NAME)."
So, the solution is to...
- set these variables directly
copy fastcgi_params to fcgiwrap_params and comment out the lines that set DOCUMENT_ROOT and SCRIPT_NAME.
include fcgiwrap_params;
fastcgi_param SCRIPT_FILENAME /usr/libexec/git-core/git-http-backend;
#or
fastcgi_param DOCUMENT_ROOT /usr/libexec/git-core/
fastcgi_param SCRIPT_NAME git-http-backend