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

add INNER_NOTIFICATION_SERVER_URL

This commit is contained in:
Junxiang Huang 2025-06-26 12:03:37 +08:00
parent 0a48dcef3a
commit 34026b0330
10 changed files with 34 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
manual/config/env.md
View File

@ -114,6 +114,9 @@ For configurations about Metadata server in `.env`, please refer [here](../exten
- `NOTIFICATION_SERVER_URL`: The [notification server](../extension/notification-server.md) url, leave blank to disable it (default).
!!! note "In Seafile cluster or standalone-deployment notification server"
In addition to `NOTIFICATION_SERVER_URL`, you also need to specify `INNER_NOTIFICATION_SERVER_URL=$NOTIFICATION_SERVER_URL`, which will be used for the connection between Seafile server and notification server.
## Cluster init configuration
- `CLUSTER_INIT_MODE`: (only valid in pro edition at deploying first time). Cluster initialization mode, in which the necessary configuration files for the service to run will be generated (but **the service will not be started**). If the configuration file already exists, no operation will be performed. The default value is `true`. When the configuration file is generated, ***be sure to set this item to `false`***.

9
manual/extension/notification-server.md
View File

@ -31,14 +31,19 @@ then add or modify `NOTIFICATION_SERVER_URL`:
=== "Deploy with Seafile"
```sh
NOTIFICATION_SERVER_URL=https://seafile.example.com/notification
NOTIFICATION_SERVER_URL=$SEAFILE_SERVER_PROTOCOL://$SEAFILE_SERVER_HOSTNAME/notification
```
=== "Standalone deployment"
```sh
NOTIFICATION_SERVER_URL=<your notification server URL>
INNER_NOTIFICATION_SERVER_URL=$NOTIFICATION_SERVER_URL
```
!!! tip "Difference between `NOTIFICATION_SERVER_URL` and `INNER_NOTIFICATION_SERVER_URL`"
- `NOTIFICATION_SERVER_URL`: used to do the connection between client (i.e., user's browser) and notification server
- `INNER_NOTIFICATION_SERVER_URL`: used to do the connection between Seafile server and notification server
Finally, You can run notification server with the following command:
```sh
@ -48,7 +53,7 @@ docker compose up -d
## Checking notification server status
When the notification server is working, you can access `http://127.0.0.1:8083/ping` from your browser, which will answer `{"ret": "pong"}`. If you have a proxy configured, you can access `https://{server}/notification/ping` from your browser instead.
When the notification server is working, you can access `http://127.0.0.1:8083/ping` from your browser, which will answer `{"ret": "pong"}`. If you have a proxy configured, you can access `https://seafile.example.com/notification/ping` from your browser instead.
## Compatible client

1
manual/repo/docker/ce/seafile-server.yml
View File

@ -72,6 +72,7 @@ services:
- REDIS_PASSWORD=${REDIS_PASSWORD:-}
- MEMCACHED_HOST=${MEMCACHED_HOST:-memcached}
- MEMCACHED_PORT=${MEMCACHED_PORT:-11211}
- INNER_NOTIFICATION_SERVER_URL=${INNER_NOTIFICATION_SERVER_URL:-http://notification-server:8083}
- NOTIFICATION_SERVER_URL=${NOTIFICATION_SERVER_URL:-}
- ENABLE_SEAFILE_AI=${ENABLE_SEAFILE_AI:-false}
- SEAFILE_AI_SERVER_URL=${SEAFILE_AI_SERVER_URL:-http://seafile-ai:8888}

1
manual/repo/docker/cluster/env
View File

@ -44,6 +44,7 @@ S3_SSE_C_KEY=
## Notification
NOTIFICATION_SERVER_URL=
INNER_NOTIFICATION_SERVER_URL=$NOTIFICATION_SERVER_URL
## Seafile AI
ENABLE_SEAFILE_AI=false

1
manual/repo/docker/cluster/seafile-server.yml
View File

@ -46,6 +46,7 @@ services:
- SITE_ROOT=${SITE_ROOT:-/}
- ENABLE_SEADOC=${ENABLE_SEADOC:-false}
- SEADOC_SERVER_URL=${SEADOC_SERVER_URL:-http://seafile.example.com/sdoc-server}
- INNER_NOTIFICATION_SERVER_URL=${INNER_NOTIFICATION_SERVER_URL:-}
- NOTIFICATION_SERVER_URL=${NOTIFICATION_SERVER_URL:-}
- ENABLE_SEAFILE_AI=${ENABLE_SEAFILE_AI:-false}
- SEAFILE_AI_SERVER_URL=$SEAFILE_AI_SERVER_URL

1
manual/repo/docker/pro/seafile-server.yml
View File

@ -84,6 +84,7 @@ services:
- S3_USE_HTTPS=${S3_USE_HTTPS:-true}
- S3_PATH_STYLE_REQUEST=${S3_PATH_STYLE_REQUEST:-false}
- S3_SSE_C_KEY=${S3_SSE_C_KEY:-}
- INNER_NOTIFICATION_SERVER_URL=${INNER_NOTIFICATION_SERVER_URL:-http://notification-server:8083}
- NOTIFICATION_SERVER_URL=${NOTIFICATION_SERVER_URL:-}
- ENABLE_SEAFILE_AI=${ENABLE_SEAFILE_AI:-false}
- SEAFILE_AI_SERVER_URL=${SEAFILE_AI_SERVER_URL:-http://seafile-ai:8888}

5
manual/repo/k8s/ce/seafile-deployment.yaml
View File

@ -111,6 +111,11 @@ spec:
configMapKeyRef:
name: seafile-env
key: MEMCACHED_PORT
- name: INNER_NOTIFICATION_SERVER_URL
valueFrom:
configMapKeyRef:
name: seafile-env
key: NOTIFICATION_SERVER_URL
- name: NOTIFICATION_SERVER_URL
valueFrom:
configMapKeyRef:

5
manual/repo/k8s/cluster/seafile-backend-deployment.yaml
View File

@ -169,6 +169,11 @@ spec:
configMapKeyRef:
name: seafile-env
key: S3_PATH_STYLE_REQUEST
- name: INNER_NOTIFICATION_SERVER_URL
valueFrom:
configMapKeyRef:
name: seafile-env
key: NOTIFICATION_SERVER_URL
- name: NOTIFICATION_SERVER_URL
valueFrom:
configMapKeyRef:

5
manual/repo/k8s/cluster/seafile-frontend-deployment.yaml
View File

@ -154,6 +154,11 @@ spec:
configMapKeyRef:
name: seafile-env
key: S3_PATH_STYLE_REQUEST
- name: INNER_NOTIFICATION_SERVER_URL
valueFrom:
configMapKeyRef:
name: seafile-env
key: NOTIFICATION_SERVER_URL
- name: NOTIFICATION_SERVER_URL
valueFrom:
configMapKeyRef:

5
manual/repo/k8s/pro/seafile-deployment.yaml
View File

@ -161,6 +161,11 @@ spec:
configMapKeyRef:
name: seafile-env
key: MEMCACHED_PORT
- name: INNER_NOTIFICATION_SERVER_URL
valueFrom:
configMapKeyRef:
name: seafile-env
key: NOTIFICATION_SERVER_URL
- name: NOTIFICATION_SERVER_URL
valueFrom:
configMapKeyRef: