mirror of
https://github.com/haiwen/seafile-admin-docs.git
synced 2025-12-25 18:22:48 +00:00
update notification server deployment & descriptions of relative variables
This commit is contained in:
parent
e9d356b9a6
commit
7a595d05b4
|
|
@ -113,10 +113,8 @@ For configurations about Metadata server in `.env`, please refer [here](../exten
|
|||
## Notification server
|
||||
|
||||
- `ENABLE_NOTIFICATION_SERVER`: Enable (`true`) or disable (`false`) notification feature for Seafile. Default is `false`.
|
||||
- `NOTIFICATION_SERVER_URL`: The [notification server](../extension/notification-server.md) url.
|
||||
|
||||
!!! 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.
|
||||
- `NOTIFICATION_SERVER_URL`: Used to do the connection between client (i.e., user's browser) and notification server. Default is `https://seafile.example.com/notification`.
|
||||
- `INNER_NOTIFICATION_SERVER_URL`: Used to do the connection between Seafile server and notification server. Default is `http://notification-server:8083`.
|
||||
|
||||
## Cluster init configuration
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,6 @@ then add or modify `ENABLE_NOTIFICATION_SERVER` and `NOTIFICATION_SERVER_URL`:
|
|||
|
||||
```sh
|
||||
ENABLE_NOTIFICATION_SERVER=true
|
||||
NOTIFICATION_SERVER_URL=$SEAFILE_SERVER_PROTOCOL://$SEAFILE_SERVER_HOSTNAME/notification
|
||||
```
|
||||
|
||||
Finally, You can run notification server with the following command:
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ services:
|
|||
- MEMCACHED_PORT=${MEMCACHED_PORT:-11211}
|
||||
- ENABLE_NOTIFICATION_SERVER=${ENABLE_NOTIFICATION_SERVER:-false}
|
||||
- INNER_NOTIFICATION_SERVER_URL=${INNER_NOTIFICATION_SERVER_URL:-http://notification-server:8083}
|
||||
- NOTIFICATION_SERVER_URL=${NOTIFICATION_SERVER_URL:-}
|
||||
- NOTIFICATION_SERVER_URL=${NOTIFICATION_SERVER_URL:-${SEAFILE_SERVER_PROTOCOL:-http}://${SEAFILE_SERVER_HOSTNAME:?Variable is not set or empty}/notification}
|
||||
- ENABLE_SEAFILE_AI=${ENABLE_SEAFILE_AI:-false}
|
||||
- SEAFILE_AI_SERVER_URL=${SEAFILE_AI_SERVER_URL:-http://seafile-ai:8888}
|
||||
- SEAFILE_AI_SECRET_KEY=${JWT_PRIVATE_KEY:?Variable is not set or empty}
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ services:
|
|||
- S3_SSE_C_KEY=${S3_SSE_C_KEY:-}
|
||||
- ENABLE_NOTIFICATION_SERVER=${ENABLE_NOTIFICATION_SERVER:-false}
|
||||
- INNER_NOTIFICATION_SERVER_URL=${INNER_NOTIFICATION_SERVER_URL:-http://notification-server:8083}
|
||||
- NOTIFICATION_SERVER_URL=${NOTIFICATION_SERVER_URL:-}
|
||||
- NOTIFICATION_SERVER_URL=${NOTIFICATION_SERVER_URL:-${SEAFILE_SERVER_PROTOCOL:-http}://${SEAFILE_SERVER_HOSTNAME:?Variable is not set or empty}/notification}
|
||||
- ENABLE_SEAFILE_AI=${ENABLE_SEAFILE_AI:-false}
|
||||
- SEAFILE_AI_SERVER_URL=${SEAFILE_AI_SERVER_URL:-http://seafile-ai:8888}
|
||||
- SEAFILE_AI_SECRET_KEY=${JWT_PRIVATE_KEY:?Variable is not set or empty}
|
||||
|
|
|
|||
|
|
@ -120,7 +120,6 @@ If you are using notification server in Seafile 12, please specify the notificat
|
|||
=== "Deploy in the same host with Seafile"
|
||||
```sh
|
||||
ENABLE_NOTIFICATION_SERVER=true
|
||||
NOTIFICATION_SERVER_URL=$SEAFILE_SERVER_PROTOCOL://$SEAFILE_SERVER_HOSTNAME/notification
|
||||
```
|
||||
=== "Standalone deployment"
|
||||
```sh
|
||||
|
|
|
|||
Loading…
Reference in New Issue