From cd561e2cc60d2ec44f659fb7d4ca90f415e424b2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E6=AC=A2=E4=B9=90=E9=A9=AC?=
<38058090+SkywalkerSpace@users.noreply.github.com>
Date: Mon, 19 May 2025 18:55:45 +0800
Subject: [PATCH] SeaDoc standalone Apache proxy (#519)
---
manual/extension/setup_seadoc.md | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/manual/extension/setup_seadoc.md b/manual/extension/setup_seadoc.md
index d376abcb..9814c181 100644
--- a/manual/extension/setup_seadoc.md
+++ b/manual/extension/setup_seadoc.md
@@ -101,6 +101,8 @@ If you deploy Seafile in a cluster or if you deploy Seafile with binary package,
4. Add a reverse proxy for SeaDoc server. In cluster environtment, it means you need to add reverse proxy rules at load balance. Here, we use Nginx as an example (**please replace `127.0.0.1:80` to `host:port` of your Seadoc server**)
+=== "Nginx"
+
```
...
server {
@@ -136,6 +138,20 @@ If you deploy Seafile in a cluster or if you deploy Seafile with binary package,
}
```
+=== "Apache"
+
+ ```
+
+ ProxyPass "http://127.0.0.1:80/"
+ ProxyPassReverse "http://127.0.0.1:80/"
+
+
+
+ # Since Apache HTTP Server 2.4.47
+ ProxyPass "http://127.0.0.1:80/socket.io/" upgrade=websocket
+
+ ```
+
5. Start SeaDoc server server with the following command
```sh