Configuration And Examples

Configuring your application

Note

See full config example. I recommend only configuring the settings you need.

Tip

You can also use Environment Variables to specify secrets and config file path.

Server Config Examples

You will need to define a source for filebrowser to run, here's a minimal example

server
  sources:
    - path: "/path/to/source"
      name: optional-name
auth:
  adminUsername: admin
  adminPassword: admin

Two source config:

server:
  port: 80
  sources:
    - path: "/path/to/source1" # defaults with name "source1"
    - path: "/path/to/source2" # defaults with name "source2"

default source configuration

There are 3 defaults to consider when configuring a source:

1. What users get access to the source by default? This is configured via defaultEnabled config. There is always 1 source minimum configured for a user. You can specify exactly which one if you specify this, otherwise, the first source in the list will be considered defaultEnabled: true.
2. What is the default user scope for a source? This is configured via defaultUserScope config. This is the default scope a user gets when a new user is created and the scopes aren't specified. However, when creating a user via the UI, you must define scopes, which mostly apply to API and CLI user creation.
3. Should a user directory be automatically created? This is configured via the createUserDir config. The default is false; it needs to be set to true to automatically happen on user creation. When true, the defaultUserScope is the base directory.
   • if you change sources, the new source will create user directories in the scope given on startup if they don't exist.
   • the user scope gets modified to be the username sub directory.

Here is an example config for defaults, where source2 is the only default a user gets with a scope in a subfolder.

server:
  sources:
    - path: "/path/to/source1"
    - path: "/path/to/source2"
      config:
        defaultUserScope: "/subfolder" # include leading slash
        defaultEnabled: true
        createUserDir: true           # "/subfolder/username" directory will be created

Example advanced source config:

with more advanced config:

server:
  port: 80
  sources:
    - name: "mysource" # optional, otherwise the source gets named the folder name
      path: "/mnt/folder"
      config: # config is totally optional, defaults applied if not configured
        exclude:
          files:
            - "/myfile.txt" # for example, corresponds to "/mnt/folder/myfile.txt"
            - "/subfolder/another.txt"
          folders:
            - "/subfolder/ignoreMe"
          fileEndsWith:
            - ".zip" # excludes any files that end with ".zip"
            - ".tar.gz"
            - "-hidden.jpg"

Auth config Examples

You can configure multiple auth methods via auth.methods, without any configuration it defaults to password auth:

auth:
  methods:
    noauth: false
    password:
      enabled: true
      minLength: 7  # set min password length requirement -- defaults to 5 if unset
      signup: false
    proxy:
      enabled: true
      header: "proxy-user"  # header which should container username
      createUser: true      # automatically creates user with default user properties

By default, the only configured Auth method will be password if not configured.

Media integration

integrations:
  media:
    ffmpegPath: "/usr/local/bin" # wherever you have both ffmpeg and ffprobe installed at

OpenID Connect configuration (OIDC)

Enabling OIDC on FileBrowser Quantum is easy and requires two main changes:

Firstly, you must add your OIDC provider information to the config.yaml, such as:

auth:
  methods:
    password:
      enabled: false # set to false if you only want to allow OIDC
    oidc:
      enabled: true                              # whether to enable OIDC authentication
      clientId: "xxx"                            # client id of the OIDC application
      clientSecret: "xxx"                        # client secret of the OIDC application
      issuerUrl: "http://localhost/application/" # authorization URL of the OIDC provider
      scopes: "email openid profile"             # scopes to request from the OIDC provider
      userIdentifier: "username"     # the user identifier to use for authentication. Default is "username", can be "email" or "username", or "phone"
      disableVerifyTLS: false        # disable TLS verification for the OIDC provider. This is insecure and should only be used for testing.
      logoutRedirectUrl: ""          # if provider logout url is provided, filebrowser will also redirect to logout url. Custom logout query params are respected.
      createUser: true               # create user if it does not exist
      adminGroup: "authentik Admins" # if set, users in this group will be granted admin privileges.

Then, the next step is to provide your OIDC provider such as Authelia or Authentik with a valid "callback URL" , so it can redirect a valid login back to filebrowser. Typically, this will be the external URL, but you may also provide an internal callback as well. An example callback URL would be https://localhost:8080/api/auth/oidc/callback where localhost:8080 is your filebrowser domain.

Note, if your have a non-default baseURL defined in your filebrowser config or proxy, your callback should include that.

Example Authelia OIDC Authentication

      - client_id: xxx
        client_name: filebrowser
        client_secret: xxx
        public: false
        authorization_policy: two_factor
        scopes:
          - openid
          - email
          - profile
        grant_types:
          - 'authorization_code' # required
        redirect_uris:
          - https://files.example.com/api/auth/oidc/callback
        userinfo_signing_algorithm: none
        token_endpoint_auth_method: client_secret_basic

Frontend Configuration Example

An example frontend configuration in your config.yaml:

frontend:
  name: "Your custom name"
  disableDefaultLinks: true
  externalLinks:
    - text: "Your custom link text"
      url: "https://example.com"
      title: "hover over me text"