From 4f49b16079b27d7ce633619e4cddfdf2bffbc952 Mon Sep 17 00:00:00 2001
From: cashmere <cashmere@autistici.org>
Date: Fri, 4 Sep 2026 09:05:24 +0200
Subject: initial commit

---
 www/scgi.wiki | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 www/scgi.wiki

(limited to 'www/scgi.wiki')

diff --git a/www/scgi.wiki b/www/scgi.wiki
new file mode 100644
index 0000000..b01431f
--- /dev/null
+++ b/www/scgi.wiki
@@ -0,0 +1,27 @@
+<title>Fossil SCGI</title>
+
+To run Fossil using SCGI, start the [/help/server|fossil server] command
+with the --scgi command-line option.  You will probably also want to
+specific an alternative TCP/IP port using --port.  For example:
+
+<pre>
+fossil server $REPOSITORY --port 9000 --scgi
+</pre>
+
+Then configure your SCGI-aware web-server to send SCGI requests to port
+9000 on the machine where Fossil is running.  A typical configuration for
+this in Nginx is:
+
+<pre>
+location ~ ^/demo_project/ {
+    include scgi_params;
+    scgi_pass localhost:9000;
+    scgi_param SCRIPT_NAME "/demo_project";
+    scgi_param HTTPS "on";
+}
+</pre>
+
+Note that Nginx does not normally send either the PATH_INFO or SCRIPT_NAME
+variables via SCGI, but Fossil needs one or the other.  So the configuration
+above needs to add SCRIPT_NAME.  If you do not do this, Fossil returns an
+error.
-- 
cgit v1.3.1