15308555518/ seafile-admin-docs
1
0
Fork 0
mirror of https://github.com/haiwen/seafile-admin-docs.git synced 2026-01-01 03:02:47 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

fix: missing

This commit is contained in:
Junxiang Huang 2024-05-14 15:01:16 +08:00
parent 52f7c8e2fa
commit 354bb0ef56
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
manual/docker/deploy_seafile_with_docker.md
View File

@ -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:

4
manual/docker/pro-edition/deploy_seafile_pro_with_docker.md
View File

@ -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: