Fossil SCM
|
1
|
<title>Fossil SCGI</title> |
|
2
|
|
|
3
|
To run Fossil using SCGI, start the [/help/server|fossil server] command |
|
4
|
with the --scgi command-line option. You will probably also want to |
|
5
|
specific an alternative TCP/IP port using --port. For example: |
|
6
|
|
|
7
|
<pre> |
|
8
|
fossil server $REPOSITORY --port 9000 --scgi |
|
9
|
</pre> |
|
10
|
|
|
11
|
Then configure your SCGI-aware web-server to send SCGI requests to port |
|
12
|
9000 on the machine where Fossil is running. A typical configuration for |
|
13
|
this in Nginx is: |
|
14
|
|
|
15
|
<pre> |
|
16
|
location ~ ^/demo_project/ { |
|
17
|
include scgi_params; |
|
18
|
scgi_pass localhost:9000; |
|
19
|
scgi_param SCRIPT_NAME "/demo_project"; |
|
20
|
scgi_param HTTPS "on"; |
|
21
|
} |
|
22
|
</pre> |
|
23
|
|
|
24
|
Note that Nginx does not normally send either the PATH_INFO or SCRIPT_NAME |
|
25
|
variables via SCGI, but Fossil needs one or the other. So the configuration |
|
26
|
above needs to add SCRIPT_NAME. If you do not do this, Fossil returns an |
|
27
|
error. |
|
28
|
|