mirror of
https://github.com/ggogel/seafile-containerized.git
synced 2024-11-16 17:05:32 +00:00
144 lines
6 KiB
Markdown
144 lines
6 KiB
Markdown
[](http://travis-ci.org/haiwen/seafile-docker)
|
|
|
|
### About
|
|
|
|
- [Docker](https://docker.com/) is an open source project to pack, ship and run any Linux application in a lighter weight, faster container than a traditional virtual machine.
|
|
|
|
- Docker makes it much easier to deploy [a Seafile server](https://github.com/haiwen/seafile) on your servers and keep it updated.
|
|
|
|
- The base image configures Seafile with the Seafile team's recommended optimal defaults.
|
|
|
|
If you are not familiar with docker commands, please refer to [docker documentation](https://docs.docker.com/engine/reference/commandline/cli/).
|
|
|
|
### Getting Started
|
|
|
|
To run the seafile server container:
|
|
|
|
```sh
|
|
docker run -d --name seafile \
|
|
-e SEAFILE_SERVER_HOSTNAME=seafile.example.com \
|
|
-v /opt/seafile-data:/shared \
|
|
-p 80:80 \
|
|
seafileltd/seafile:latest
|
|
```
|
|
|
|
Wait for a few minutes for the first time initialization, then visit `http://seafile.example.com` to open Seafile Web UI.
|
|
|
|
This command will mount folder `/opt/seafile-data` at the local server to the docker instance. You can find logs and other data under this folder.
|
|
|
|
### More configuration Options
|
|
|
|
#### Custom Admin Username and Password
|
|
|
|
The default admin account is `me@example.com` and the password is `asecret`. You can use a different password by setting the container's environment variables:
|
|
e.g.
|
|
|
|
```sh
|
|
docker run -d --name seafile \
|
|
-e SEAFILE_SERVER_HOSTNAME=seafile.example.com \
|
|
-e SEAFILE_ADMIN_EMAIL=me@example.com \
|
|
-e SEAFILE_ADMIN_PASSWORD=a_very_secret_password \
|
|
-v /opt/seafile-data:/shared \
|
|
-p 80:80 \
|
|
seafileltd/seafile:latest
|
|
```
|
|
|
|
If you forget the admin password, you can add a new admin account and then go to the sysadmin panel to reset user password.
|
|
|
|
#### Let's encrypt SSL certificate
|
|
|
|
If you set `SEAFILE_SERVER_LETSENCRYPT` to `true`, the container would request a letsencrypt-signed SSL certificate for you automatically.
|
|
|
|
e.g.
|
|
|
|
```
|
|
docker run -d --name seafile \
|
|
-e SEAFILE_SERVER_LETSENCRYPT=true \
|
|
-e SEAFILE_SERVER_HOSTNAME=seafile.example.com \
|
|
-e SEAFILE_ADMIN_EMAIL=me@example.com \
|
|
-e SEAFILE_ADMIN_PASSWORD=a_very_secret_password \
|
|
-v /opt/seafile-data:/shared \
|
|
-p 80:80 \
|
|
-p 443:443 \
|
|
seafileltd/seafile:latest
|
|
```
|
|
|
|
If you want to use your own SSL certificate:
|
|
- create a folder `/opt/seafile-data/ssl`, and put your certificate and private key under the ssl directory.
|
|
- Assume your site name is `seafile.example.com`, then your certificate must have the name `seafile.example.com.crt`, and the private key must have the name `seafile.example.com.key`.
|
|
|
|
#### Modify Seafile Server Configurations
|
|
|
|
The config files are under `shared/seafile/conf`. You can modify the configurations according to [Seafile manual](https://manual.seafile.com/)
|
|
|
|
After modification, you need to restart the container:
|
|
|
|
```
|
|
docker restart seafile
|
|
```
|
|
|
|
#### Find logs
|
|
|
|
The seafile logs are under `shared/logs/seafile` in the docker, or `/opt/seafile-data/logs/seafile` in the server that run the docker.
|
|
|
|
The system logs are under `shared/logs/var-log`, or `/opt/seafile-data/logs/var-log` in the server that run the docker.
|
|
|
|
#### Add a new Admin
|
|
|
|
Ensure the container is running, then enter this command:
|
|
|
|
```
|
|
docker exec -it seafile /opt/seafile/seafile-server-latest/reset-admin.sh
|
|
```
|
|
|
|
Enter the username and password according to the prompts. You now have a new admin account.
|
|
|
|
### Directory Structure
|
|
|
|
#### `/shared`
|
|
|
|
Placeholder spot for shared volumes. You may elect to store certain persistent information outside of a container, in our case we keep various logfiles and upload directory outside. This allows you to rebuild containers easily without losing important information.
|
|
|
|
- /shared/db: This is the data directory for mysql server
|
|
- /shared/seafile: This is the directory for seafile server configuration and data.
|
|
- /shared/logs: This is the directory for logs.
|
|
- /shared/logs/var-log: This is the directory that would be mounted as `/var/log` inside the container. For example, you can find the nginx logs in `shared/logs/var-log/nginx/`.
|
|
- /shared/logs/seafile: This is the directory that would contain the log files of seafile server processes. For example, you can find seaf-server logs in `shared/logs/seafile/seafile.log`.
|
|
- /shared/ssl: This is directory for certificate, which does not exist by default.
|
|
|
|
### Upgrading Seafile Server
|
|
|
|
TO upgrade to latest version of seafile server:
|
|
|
|
```sh
|
|
docker pull seafileltd/seafile:latest
|
|
docker rm -f seafile
|
|
docker run -d --name seafile \
|
|
-e SEAFILE_SERVER_LETSENCRYPT=true \
|
|
-e SEAFILE_SERVER_HOSTNAME=seafile.example.com \
|
|
-e SEAFILE_ADMIN_EMAIL=me@example.com \
|
|
-e SEAFILE_ADMIN_PASSWORD=a_very_secret_password \
|
|
-v /opt/seafile-data:/shared \
|
|
-p 80:80 \
|
|
-p 443:443 \
|
|
seafileltd/seafile:latest
|
|
```
|
|
|
|
If you are one of the early users who use the `launcher` script, you should refer to [upgrade from old format](https://github.com/haiwen/seafile-docker/blob/master/upgrade_from_old_format.md) document.
|
|
|
|
### Garbage Collection
|
|
|
|
When files are deleted, the blocks comprising those files are not immediately removed as there may be other files that reference those blocks (due to the magic of deduplication). To remove them, Seafile requires a ['garbage collection'](https://manual.seafile.com/maintain/seafile_gc.html) process to be run, which detects which blocks no longer used and purges them. (NOTE: for technical reasons, the GC process does not guarantee that _every single_ orphan block will be deleted.)
|
|
|
|
The required scripts can be found in the `/scripts` folder of the docker container. To perform garbage collection, simply run `docker exec seafile /scripts/gc.sh`. For the community edition, this process will stop the seafile server, but it is a relatively quick process and the seafile server will start automatically once the process has finished. The Professional supports an online garbage collection.
|
|
|
|
### Troubleshooting
|
|
|
|
You can run docker commands like "docker logs" or "docker exec" to find errors.
|
|
|
|
```sh
|
|
docker logs -f seafile
|
|
# or
|
|
docker exec -it seafile bash
|
|
```
|