Self-host Seafile on a VPS

Self-hosted file sync and share with real file-level versioning and client-side encryption options.

levelrail-cli templates deploy seafile --name my-seafile

Specification

Status
Listed
Category
Storage
Services
mariadb, memcached, seafile
Ports
80
Volumes
2
Memory
about 1 GiB
arm64
image published
amd64
image published
Settings to fill in
none

About Seafile

Self-hosted file sync and share with real file-level versioning and client-side encryption options. Runs 3 containers (mariadb, memcached, seafile), with seafile listening on port 80 and keeps its data in named volumes.

What it deploys

Seafile runs as 3 services in a single Compose app, listening on port 80, with 2 named volume mounts.

ServiceImageTagPortsVolumes
mariadb mariadb 11 none seafile_mariadb_data -> /var/lib/mysql
memcached memcached latest none none
seafile seafileltd/seafile-mc 13.0.28 80 seafile_data -> /shared

Before you install

  • CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
  • Listed. It is in the catalog. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 80 directly on the host, so open them in the VPS firewall only if you want that.
  • Review. Image is not pinned to a version tag, so a redeploy can pull different code (memcached:latest).

Settings and environment

You do not have to fill in anything. 8 secrets are generated at deploy and stored encrypted. Values are never shown here.

ServiceVariableValue
mariadbMYSQL_DATABASEPreset by the template
mariadbMYSQL_PASSWORDGenerated at deploy
mariadbMYSQL_ROOT_PASSWORDGenerated at deploy
mariadbMYSQL_USERGenerated at deploy
seafileCACHE_PROVIDERPreset by the template
seafileINIT_SEAFILE_ADMIN_EMAILPreset by the template
seafileINIT_SEAFILE_ADMIN_PASSWORDGenerated at deploy
seafileINIT_SEAFILE_MYSQL_ROOT_PASSWORDGenerated at deploy
seafileJWT_PRIVATE_KEYGenerated at deploy
seafileMEMCACHED_HOSTPreset by the template
seafileMEMCACHED_PORTPreset by the template
seafileSEAFILE_MYSQL_DB_CCNET_DB_NAMEPreset by the template
seafileSEAFILE_MYSQL_DB_HOSTPreset by the template
seafileSEAFILE_MYSQL_DB_PASSWORDGenerated at deploy
seafileSEAFILE_MYSQL_DB_PORTPreset by the template
seafileSEAFILE_MYSQL_DB_SEAFILE_DB_NAMEPreset by the template
seafileSEAFILE_MYSQL_DB_SEAHUB_DB_NAMEPreset by the template
seafileSEAFILE_MYSQL_DB_USERGenerated at deploy
seafileSEAFILE_SERVER_HOSTNAMEPreset by the template
seafileSEAFILE_SERVER_PROTOCOLPreset by the template
seafileTIME_ZONEPreset by the template

Install Seafile on a VPS

  1. Install Levelrail on a fresh VPS

    Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.

    curl -fsSL https://levelrail.com/install.sh | sudo sh
  2. Sign in

    Open the setup link, choose a password, then log the CLI in. The CLI install command is curl -fsSL https://levelrail.com/install-cli.sh | sh if the machine does not have it. See Getting started.

    levelrail-cli login --device
  3. Read the template

    Shows the entry, including its full compose.yaml.

    levelrail-cli templates get seafile
  4. Deploy it

    This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.

    levelrail-cli templates deploy seafile --name my-seafile

Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Seafile.

More in Storage

All Storage templates