Installation

File Browser is a single binary and can be used as a standalone executable. Although, some might prefer to use it with Docker or Caddy, which is a fantastic web server that enables HTTPS by default. Its installation is quite straightforward independently on which system you want to use.

Quick Setup

The quickest way for beginners to start using File Browser is by opening your terminal and executing the following commands:

Brew

brew tap filebrowser/tap
brew install filebrowser
filebrowser -r /path/to/your/files

Unix

curl -fsSL https://raw.githubusercontent.com/filebrowser/get/master/get.sh | bash
filebrowser -r /path/to/your/files

Windows

iwr -useb https://raw.githubusercontent.com/filebrowser/get/master/get.ps1 | iex
filebrowser -r /path/to/your/files

Configuring

Done! It will bootstrap a database in which all the configurations and users are stored. Now, you can see on your command line the address in which your instance is running. You just need to go to that URL and use the following credentials:

Username: admin
Password: (printed in your console)

Although this is the fastest way to bootstrap an instance, we recommend you to take a look at other possible options, by checking config init --help and config set --help, to make the installation as safe and customized as it can be.

Docker

File Browser is available as two different Docker images, which can be found on Docker Hub.

Alpine

docker run \
  -v /path/to/srv:/srv \
  -v /path/to/filebrowser.db:/database.db \
  -v /path/to/.filebrowser.json:/.filebrowser.json \
  -u $(id -u):$(id -g) \
  -p 8080:80 \
  filebrowser/filebrowser

Where:

/path/to/srv contains the files root directory for File Browser
/path/to/filebrowser.db is the database.db
/path/to/database is the .filebrowser.json

Warning

To use this image correctly, you need to first initialize a File Browser database outside of the Docker image and then start the Docker image with the database mounted. Otherwise, Docker will create an empty directory at the mounting point and fail to start.

s6 overlay

The s6 image is based on LinuxServer and leverages the s6-overlay system for a standard, highly customizable image. It should be used as follows:

docker run \
  -v /path/to/srv:/srv \
  -v /path/to/database:/database \
  -v /path/to/config:/config \
  -e PUID=$(id -u) \
  -e PGID=$(id -g) \
  -p 8080:80 \
  filebrowser/filebrowser:s6