Good afternoon. I’m testing seadoc, but I can’t stock up. There is a docker compose configuration (incomplete file):
COMPOSE_FILE='seafile-server.yml,notification-server.yml,seadoc.yml'
COMPOSE_PATH_SEPARATOR=','
SEAFILE_SERVER_HOSTNAME=sfile.xxx.ru
SEAFILE_SERVER_PROTOCOL=https
...
ENABLE_SEADOC=true
Seadoc has just started setting up (everything else is already working)
seadoc:
image: ${SEADOC_IMAGE}
container_name: seafile-seadoc
restart: unless-stopped
volumes:
- ${SEADOC_VOLUME}:/shared
# ports:
# - "8082:80"
environment:
- DB_HOST=${SEAFILE_MYSQL_DB_HOST:-db}
- DB_PORT=${SEAFILE_MYSQL_DB_PORT:-3306}
- DB_USER=${SEAFILE_MYSQL_DB_USER:-seafile}
- DB_PASSWORD=${SEAFILE_MYSQL_DB_PASSWORD}
- DB_NAME=${SEADOC_MYSQL_DB_NAME:-${SEAFILE_MYSQL_DB_SEAHUB_DB_NAME:-seahub_db}}
- TIME_ZONE=${TIME_ZONE}
- JWT_PRIVATE_KEY=${JWT_PRIVATE_KEY}
# - NON_ROOT=${NON_ROOT:-}
- SEAHUB_SERVICE_URL=${SEAFILE_SERVER_HOSTNAME}
seafile:
- ENABLE_SEADOC=true
- SEADOC_SERVER_URL=${SEAFILE_SERVER_PROTOCOL:-https}://${SEAFILE_SERVER_HOSTNAME}/sdoc-server
The containers are in the same network.
As an nginx proxy, seadoc is available from the nginx container.
....
location / {
proxy_pass http://seafile:80;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $server_name;
# proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Proto https;
proxy_set_header Connection "";
....
location /sdoc-server/ {
proxy_pass http://seafile-seadoc:80/;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $server_name;
proxy_set_header X-Forwarded-Proto $scheme;
....
location /socket.io {
proxy_pass http://seafile-seadoc:80;
....
If you open the link - https://sfile.xxx.ru/sdoc-server/
Welcome to sdoc-server. The current version is 2.0.9