← Templates · Applications
SE
Seafile
Community3 services
Self-hosted file sync and share — a private Dropbox/Google Drive alternative with versioning and team libraries.
| Runs | 3 services |
|---|---|
| Stack | seafile-dbseafile-memcachedseafile |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Not yet |
Why deploy on Railyard
Railyard provisions all 3 services in this stack together — seafile-db, seafile-memcached, seafile — wired to reach each other over the private network, on a server you already pay for.
Deploying Seafile is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- A private, self-hosted alternative to Dropbox/Google Drive for a team
- File sync across desktop/mobile clients with versioning and team libraries
- Shared links and permissions for files without a third-party storage vendor
Good to know
- Seafile's own first-boot setup creates its databases using MySQL root credentials, so this stack runs a dedicated MariaDB with a known root password rather than using Railyard's shared mysql addon, which only grants scoped per-app access
- Seafile creates its admin account automatically on first boot (admin@example.com, with a generated password) rather than through a setup wizard — find the real password on the seafile service's env vars page before logging in
- Desktop/mobile sync clients talk to the seafile service's own sync API on this stack's public port; large uploads can be slow on a small server