15308555518/ seafile-admin-docs
1
0
Fork 0
mirror of https://github.com/haiwen/seafile-admin-docs.git synced 2025-12-26 02:32:50 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Move notification server in cluster

This commit is contained in:
杨赫然 2024-03-15 16:18:52 +08:00
parent 79618311fc
commit 5911569979
3 changed files with 63 additions and 63 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

63
manual/deploy/notification-server.md
View File

@ -134,3 +134,66 @@ If the client works with notification server, there should be a log message in s
```
Notification server is enabled on the remote server xxxx
```
## Notification Server in Seafile cluster
In Seafile Pro edition, the notification server is the same as community edition notification server.
If you enable [clustering](../deploy_pro/deploy_in_a_cluster.md), You need to deploy notification server on one of the servers. The load balancer should forward websockets requests to this node. The notification server configuration corresponding to each node of the cluster is as follows.
The notification server configuration should be the same as in community edition:
```
[notification]
enabled = true
# the ip of notification server.
host = 192.168.1.134
# the port of notification server
port = 8083
# the log level of notification server
log_level = info
# jwt_private_key is used to generate jwt token and authenticate seafile server
jwt_private_key = M@O8VWUb81YvmtWLHGB2I_V7di5-@0p(MF*GrE!sIws23F
```
You need to configure load balancing according to the following forwarding rules:
1. Forward `/notification/ping` requests to notification server via http protocol.
2. Forward websockets requests with URL prefix `/notification` to notification server.
Here is a configuration that uses haproxy to support notification server, and haproxy version needs to be >= 2.0.
You should use similar configurations for the other load balancers.
```
#/etc/haproxy/haproxy.cfg
# Other existing haproxy configurations
......
frontend seafile
bind 0.0.0.0:80
mode http
option httplog
option dontlognull
option forwardfor
acl notif_ping_request url_sub -i /notification/ping
acl ws_requests url_sub -i /notification
acl hdr_connection_upgrade hdr(Connection) -i upgrade
acl hdr_upgrade_websocket hdr(Upgrade) -i websocket
use_backend ws_backend if hdr_connection_upgrade hdr_upgrade_websocket
use_backend notif_ping_backend if notif_ping_request
use_backend ws_backend if ws_requests
default_backend backup_nodes
backend backup_nodes
cookie SERVERID insert indirect nocache
server seafileserver01 192.168.0.137:80
backend notif_ping_backend
option forwardfor
server ws 192.168.0.137:8083
backend ws_backend
option forwardfor # This sets X-Forwarded-For
server ws 192.168.0.137:8083
```

62
manual/deploy_pro/notification-server.md
View File

@ -1,62 +0,0 @@
# Notification Server in Seafile cluster
In Seafile Pro edition, the notification server is the same as [community edition notification server](../deploy/notification-server.md).
If you enable [clustering](./deploy_in_a_cluster.md), You need to deploy notification server on one of the servers. The load balancer should forward websockets requests to this node. The notification server configuration corresponding to each node of the cluster is as follows.
The notification server configuration should be the same as in community edition:
```
[notification]
enabled = true
# the ip of notification server.
host = 192.168.1.134
# the port of notification server
port = 8083
# the log level of notification server
log_level = info
# jwt_private_key is used to generate jwt token and authenticate seafile server
jwt_private_key = M@O8VWUb81YvmtWLHGB2I_V7di5-@0p(MF*GrE!sIws23F
```
You need to configure load balancing according to the following forwarding rules:
1. Forward `/notification/ping` requests to notification server via http protocol.
2. Forward websockets requests with URL prefix `/notification` to notification server.
Here is a configuration that uses haproxy to support notification server, and haproxy version needs to be >= 2.0.
You should use similar configurations for the other load balancers.
```
#/etc/haproxy/haproxy.cfg
# Other existing haproxy configurations
......
frontend seafile
bind 0.0.0.0:80
mode http
option httplog
option dontlognull
option forwardfor
acl notif_ping_request url_sub -i /notification/ping
acl ws_requests url_sub -i /notification
acl hdr_connection_upgrade hdr(Connection) -i upgrade
acl hdr_upgrade_websocket hdr(Upgrade) -i websocket
use_backend ws_backend if hdr_connection_upgrade hdr_upgrade_websocket
use_backend notif_ping_backend if notif_ping_request
use_backend ws_backend if ws_requests
default_backend backup_nodes
backend backup_nodes
cookie SERVERID insert indirect nocache
server seafileserver01 192.168.0.137:80
backend notif_ping_backend
option forwardfor
server ws 192.168.0.137:8083
backend ws_backend
option forwardfor # This sets X-Forwarded-For
server ws 192.168.0.137:8083
```

1
mkdocs.yml
View File

@ -72,7 +72,6 @@ nav:
- Deploy in a cluster: deploy_pro/deploy_in_a_cluster.md
- Search and background tasks in a cluster: deploy_pro/enable_search_and_background_tasks_in_a_cluster.md
- Memcache and MariaDB Cluster: deploy_pro/memcached_mariadb_cluster.md
- Notification Server in Cluster: deploy_pro/notification-server.md
- Setup Seafile cluster with NFS: deploy_pro/setup_seafile_cluster_with_nfs.md
- License: deploy_pro/seafile_professional_sdition_software_license_agreement.md
- Seafile Setup with Docker: