https://github.com/gtsteffaniak/filebrowser
File browser Quantum is the shiny feature rich fork!
I have also used filestash with some success
this post was submitted on 18 Jun 2025
113 points (99.1% liked)
Selfhosted
46676 readers
625 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
I was going to query why fork instead of just maintaining, but after reading theose comments I see the problem.
So, ok, I need to start shifting packages...
Reckon I can get this going somewhere where I don't have sudo?
I doubt it, why dont you have sudo?
Trying to set that up to try out, but I can't get it to see/use my config.yaml.
/srv/filebrowser-new/data/config.yaml
volumes:
- /srv/filebrowser-new/data:/config environment:
- FILEBROWSER_CONFIG="/config/config.yaml"
Says '/config/config.yaml' doesn't exist and will not start. Same thing if I mount the config file directly, instead of just its folder.
If I remove the env var, it changes to "could not open config file 'config.yaml', using default settings" and starts at least. From there I can 'ls -l' through docker exec and see that my config is mounted exactly where it's supposed to be '/config/config.yaml' and has 777 perms, but filebrowser insists it doesn't exist...
My config is just the example for now.
I don't understand what I could possibly be doing wrong.
/edit: three hours of messing around and I figured it out:
- FILEBROWSER_CONFIG="/config/config.yaml"
Must not have quotation marks. Removed them and now it's working.
Must not have quotation marks. Removed them and now it's working.
Man that's finicky...
It's just YAML, if you do FILEBROWSER_CONFIG:"/config/config.yaml" instead it might work with quotes.
Dev replied to my github discussion.
Apparently it's an issue with array style env variable layout.
environment:
key:"value"
Instead of
environment:
- key=valueSo it's a YAML quirk then?
I'm not sure whether this is specific to this project, docker, or YAML in general.
Looking through my other 20 or so compose files, I use the array notation for most of my environment variables, but I don't have any double quotation marks elsewhere. Maybe they're not supposed to work in this format, idk.
Good to keep in mind I guess.
When the stable release is published, it's honestly a no brainer. Although Filestash is a good alternative too.
Ive had some good experience with filestash but recently they swapped to collabora which brought me a host of headaches.
The Dev is awesome though.
Ah, this makes sense now. I was wondering why it hadn't been updated in a while, that was my only hangup.
I saw this the other day as well when i was looking at filebrowsers github looking into seeing if it had SSO support. It's a shame really.