From 3e9e6fef948b5f419af1720b4aca0274c0a7fd1f Mon Sep 17 00:00:00 2001 From: Daniel Pan Date: Thu, 12 Aug 2021 11:26:51 +0800 Subject: [PATCH] Update using_sqlite.md --- manual/deploy/using_sqlite.md | 20 +------------------- 1 file changed, 1 insertion(+), 19 deletions(-) diff --git a/manual/deploy/using_sqlite.md b/manual/deploy/using_sqlite.md index d9a24950..89ef67e1 100644 --- a/manual/deploy/using_sqlite.md +++ b/manual/deploy/using_sqlite.md @@ -263,27 +263,9 @@ pkill -f seafile-controller pkill -f "seahub" ``` -## Setup in non-interactive way - -Since Seafile version 5.1.4, `setup-seafile.sh` supports auto mode. You can run the setup script in non-interactive by supply the needed parameters via script parameters or environment variables. - -```sh -cd seafile-server-* -./setup-seafile.sh auto [param1] [param2]... -``` - -Related parameters as follow: - -Option | Script parameter | Environment variable | Default value ---------|--------|--------|-------- -server name | -n | SERVER_NAME | hostname -s(short host name) -server ip or domain | -i |SERVER_IP | hostname -i(address for the host name) -fileserver port | -p | FILESERVER_PORT | 8082 -seafile data dir | -d | SEAFILE_DIR | current directory - -**Note: If both script parameter and environment variable assigned, script parameter has higher priority. If neither script parameter nor environment variable assigned, default value will be used.** ## That's it! + For a production server we highly recommend to setup with Nginx/Apache and enable SSL/TLS. That's it! Now you might want read more about Seafile.