Self-host Dufs with Levelrail

A tiny file server with uploads, downloads, search and WebDAV over one login. Apache-2.0 licensed. The admin password is generated for you.

  • Authorsigoden
  • LicenceApache-2.0
  • Memory32 MiB
  • Services1

How to self-host Dufs

  1. Pull the images

    One image is pulled on your server.

    Show images
    • sigoden/dufs:v0.47.0
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 5000.

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 2 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Sign in as admin with the generated password, then upload and share files, or mount the same address as WebDAV.

Dufs requirements

Memory
About 32 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
5000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Dufs. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Dufs docs page.

Deploy Dufs your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Dufs from the CLI

levelrail-cli templates deploy dufs --name my-dufs

Deploy Dufs with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/dufs/deploy

Dufs configuration

Dufs services

ServiceImagePortsVolumes
dufs sigoden/dufs:v0.47.0 5000 data -> /data

Dufs environment variables

VariableServiceValue
DUFS_ALLOW_ALL dufs Preset by the template
DUFS_AUTH dufs Generated at deploy
DUFS_SERVE_PATH dufs Preset by the template

Ports and volumes

Ports
5000
Volumes
1 named mount: data -> /data

Dufs FAQ

How much memory does Dufs need?

The catalog lists about 32 MiB of memory for Dufs.

Does Dufs run on arm64?

For Dufs, arm64 support is not confirmed; amd64 is unknown.

What licence is Dufs under?

Dufs is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does Dufs need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which ports does Dufs use?

Dufs listens on port 5000 inside the stack.

Where does Dufs keep its data?

In a named volume: data mounted at /data.

Can I deploy Dufs on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Dufs, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image sigoden/dufs:v0.47.0 is what you deploy there.

levelrail-cli templates deploy dufs --name my-dufs