From 354bb0ef56f12380fa91a9bbd0d1a96e1a8bdff8 Mon Sep 17 00:00:00 2001 From: Junxiang Huang Date: Tue, 14 May 2024 15:01:16 +0800 Subject: [PATCH] fix: missing --- manual/docker/deploy_seafile_with_docker.md | 4 ++-- manual/docker/pro-edition/deploy_seafile_pro_with_docker.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/manual/docker/deploy_seafile_with_docker.md b/manual/docker/deploy_seafile_with_docker.md index 92f3106d..e3020561 100644 --- a/manual/docker/deploy_seafile_with_docker.md +++ b/manual/docker/deploy_seafile_with_docker.md @@ -219,7 +219,7 @@ seafile: ``` -Then create a seafile user on the host, and modify the owner to seafile in /opt/seafile-data/seafile/. (NOTE: Do not change the uid and gid.) +Then create a seafile user on the host, and modify the owner to seafile in `/opt/seafile-data/seafile/`. (NOTE: Do not change the uid and gid.) ``` groupadd --gid 8000 seafile @@ -229,7 +229,7 @@ useradd --home-dir /home/seafile --create-home --uid 8000 --gid 8000 --shell /bi chown -R seafile:seafile /opt/seafile-data/seafile/ ``` -If the files in/opt/seafile-data/seafile involve operations by other users on the host, we suggest adding `NON-ROOT-CHOWN-FILES=true` to Docker Compose.yml. In this case, every time the seafile service is started, an automatically owner change operation for /opt/seafile-data/seafile/ will be executed. But if you have a large number of files, it will consume a lot of time to start seafile. +If the files in `/opt/seafile-data/seafile` involve operations by other users on the host, we suggest adding `NON-ROOT-CHOWN-FILES=true` to Docker Compose.yml. In this case, every time the seafile service is started, an automatically owner change operation for `/opt/seafile-data/seafile/` will be executed. But if you have a large number of files, it will consume a lot of time to start seafile. ``` seafile: diff --git a/manual/docker/pro-edition/deploy_seafile_pro_with_docker.md b/manual/docker/pro-edition/deploy_seafile_pro_with_docker.md index fff80d2a..a7bb8f5d 100644 --- a/manual/docker/pro-edition/deploy_seafile_pro_with_docker.md +++ b/manual/docker/pro-edition/deploy_seafile_pro_with_docker.md @@ -309,7 +309,7 @@ seafile: ... ``` -Then create a seafile user on the host, and modify the owner to seafile in /opt/seafile-data/seafile/. (NOTE: Do not change the uid and gid.) +Then create a seafile user on the host, and modify the owner to seafile in `/opt/seafile-data/seafile/`. (NOTE: Do not change the uid and gid.) ``` groupadd --gid 8000 seafile @@ -317,7 +317,7 @@ useradd --home-dir /home/seafile --create-home --uid 8000 --gid 8000 --shell /bi chown -R seafile:seafile /opt/seafile-data/seafile/ ``` -If the files in/opt/seafile-data/seafile involve operations by other users on the host, we suggest adding `NON-ROOT-CHOWN-FILES=true` to Docker Compose.yml. In this case, every time the seafile service is started, an automatically owner change operation for /opt/seafile-data/seafile/ will be executed. But if you have a large number of files, it will consume a lot of time to start seafile. +If the files in `/opt/seafile-data/seafile` involve operations by other users on the host, we suggest adding `NON-ROOT-CHOWN-FILES=true` to Docker Compose.yml. In this case, every time the seafile service is started, an automatically owner change operation for `/opt/seafile-data/seafile/` will be executed. But if you have a large number of files, it will consume a lot of time to start seafile. ``` seafile: