Deploy and Host FileRise on Railway

About Hosting FileRise

FileRise is a lightweight self-hosted file manager with browser uploads, folder permissions, WebDAV, and encrypted folders. This template deploys FileRise v3.26.1 as one digest-pinned service with one persistent /data volume.

Common Use Cases

A small personal or team file portal.
Browser-based file upload and download.
A narrowly permissioned WebDAV endpoint.
Encrypted folders whose recovery key is retained separately.

Dependencies for FileRise Hosting

Deployment Dependencies

The template creates one service, one public HTTP domain, and one volume at /data. Railway generates first-boot admin and WebDAV passwords, a token key, and an encryption master key. A pre-bind, per-file atomic, fail-closed bootstrap creates both users before the service becomes public; WebDAV access remains disabled until an administrator enables it and grants the dedicated non-admin account a folder ACL. After first boot, passwords are changed in the FileRise UI; changing Railway bootstrap variables does not update persisted user hashes.

Uploads, users, and metadata persist on /data. Serverless is disabled and one replica is required. ClamAV, OnlyOffice, Pro features, database, cache, Bucket, worker, and cron services are not included.

Why Deploy FileRise on Railway?

Railway provides the build, TLS domain, generated secrets, health checks, restart policy, metrics, and volume. The wrapper closes FileRise's first-admin race, maps all required writable paths into one volume, and removes source secret names from the long-running process environment.

Build and image-pull time varies. R5 reached terminal success within an approximately eight-minute complete proof lifetime and passed the configured 60-second health window after container start; neither observation is a precise build-time promise.

Back up /data and the encryption master key separately. A wrong key can produce a zero-byte response, so restore checks must use byte counts and checksums. This independent community template supports its wrapper and documented Railway contract; upstream FileRise features and Railway platform incidents remain with their respective owners.