Set up Filebrowser in Coolify with perisitent user

The default set up of Coolify’s File Browser is to always gennerate a password.

Here’s the default YAML

Pay attention to the database.db part, that comes in handly later.

The default YAML is functional, exept it generates a new password every time I reset the instance. Looking at the log, I see that filebrowser.db can’t be found. Not a deal breaker, I can just look  up the password in my server.
Also I want Filebrowser to run a script whenever files are uploaded to specific folders, these settings, along with the users data are saved in filebrowser.db. This is a deal breaker.

Looking at the log, I see that the database should be named filebrowser.db, and it should be placed in /database/. Easy fix.
I tried to create the folder and mount the folder into FileBrowser’s container, that didn’t work because docker assume filebrowser.db is a directory name
I created the folder, and create the file (use touch), then I bind folder database along with filebrowser.db, this works but now FileBrowser doesn’t generate a password for first login.

Gemini suggests me to add in a hashed password as variables in Coolify, this didn’t work as well.

I deleted filebrowser.db, letting FileBrowser generate that file instead, but keeping the folder bind. This works.

Now I have a working FileBrowser. Yay me.

Add this in YAML ability to run scripts.

environment: – FB_DISABLE_EXEC=false