Self-host FileBrowser Quantum with Levelrail

Verified

A web file manager with a fast index, search, sharing links and per-user access. Apache-2.0 fork of FileBrowser. Runs in one container; the admin password is generated and shown in the service environment settings.

  • AuthorgtsteffaniakVerified by Levelrail
  • LicenceApache-2.0
  • Memory128 MiB
  • Archarm64
  • Services1

How to self-host FileBrowser Quantum

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/gtsteffaniak/filebrowser:2.0.2-stable
  2. Create the app

    One service starts in a single Compose app, with 2 named volume mounts for your data, on port 80.

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 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 from the service environment settings.

FileBrowser Quantum requirements

Memory
About 128 MiB
Architectures
amd64 image published, arm64 tested
Ports
80
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, permissive license
  • Verified. Verified on arm64 with image tag 2.0.2-stable. Our CI ran this exact image version and it answered on its health path. Evidence

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then FileBrowser Quantum. 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 FileBrowser Quantum docs page.

Deploy FileBrowser Quantum your way

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

Deploy FileBrowser Quantum from the CLI

levelrail-cli templates deploy filebrowser-quantum --name my-filebrowser-quantum

Deploy FileBrowser Quantum 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/filebrowser-quantum/deploy

FileBrowser Quantum configuration

FileBrowser Quantum services

ServiceImagePortsVolumes
filebrowser ghcr.io/gtsteffaniak/filebrowser:2.0.2-stable 80 data -> /home/filebrowser/datafiles -> /srv

FileBrowser Quantum environment variables

VariableServiceValue
FILEBROWSER_ADMIN_PASSWORD filebrowser Generated at deploy

Ports and volumes

Ports
80
Volumes
2 named mounts: data -> /home/filebrowser/data, files -> /srv

FileBrowser Quantum FAQ

How much memory does FileBrowser Quantum need?

The catalog lists about 128 MiB of memory for FileBrowser Quantum.

Does FileBrowser Quantum run on arm64?

For FileBrowser Quantum, arm64 is tested; amd64 is image published.

What licence is FileBrowser Quantum under?

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

Does FileBrowser Quantum need configuration before it starts?

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

Which ports does FileBrowser Quantum use?

FileBrowser Quantum listens on port 80 inside the stack.

Where does FileBrowser Quantum keep its data?

In named volumes: data mounted at /home/filebrowser/data and files mounted at /srv.

Can I deploy FileBrowser Quantum 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 FileBrowser Quantum, 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 ghcr.io/gtsteffaniak/filebrowser:2.0.2-stable is what you deploy there.

levelrail-cli templates deploy filebrowser-quantum --name my-filebrowser-quantum