Warning
Starting with v0.2.0, ALL configuration is done via filebrowser.yaml
Configuration file.
Starting with v0.2.4 ALL share links need to be re-created (due to
security fix).
FileBrowser Quantum is a fork of the filebrowser opensource project with the following changes:
- Enhanced lightning fast indexed search
- Real-time results as you type
- Works with more type filters
- Enhanced interactive results page.
- Revamped and simplified GUI navbar and sidebar menu.
- Additional compact view mode as well as refreshed view mode styles.
- Revamped and simplified configuration via
filebrowser.ymlconfig file. - Faster listing browsing
- Switching view modes is instant
- Changing Sort order is instant
- The entire directory is loaded in 1/3 the time
FileBrowser Quantum provides a file managing interface within a specified directory and can be used to upload, delete, preview, rename, and edit your files. It allows the creation of multiple users and each user can have its directory.
This repository is a fork of the original filebrowser with a collection of changes that make this program work better in terms of aesthetics and performance. Improved search, simplified ui (without removing features) and more secure and up-to-date build are just a few examples.
FileBrowser Quantum differs significantly to the original. There are hundreds of thousands of lines changed and they are generally no longer compatible with each other. This has been intentional -- the focus of this fork is on a few key principles:
- Simplicity and improved user experience
- Improving performance and faster feedback when making changes.
- Minimize external dependencies and standard library usage.
- Of course -- adding much-needed features.
One way you can observe the improved user experience is how I changed the UI. The Navbar is simplified to a three-component system :
- (Left) The slide-out action panel button
- (Middle) The powerful search bar.
- (Right) The view change toggle.
All other functions are moved either into the action menu or popup menus. If the action does not depend on context, it will exist in the slide-out action panel. If the action is available based on context, it will show up as a popup menu.
Using docker:
- docker run (no persistent db):
docker run -it -v /path/to/folder:/srv -p 80:80 gtstef/filebrowser
- docker compose:
- with local storage
version: '3.7'
services:
filebrowser:
volumes:
- '/path/to/folder:/srv' # required (for now not configurable)
- './database:/database' # optional if you want db to persist - configure a path under "database" dir in config file.
- './filebrowser.yaml:/filebrowser.yaml' # required
ports:
- '80:80'
image: gtstef/filebrowser
restart: always
- with network share
version: '3.7'
services:
filebrowser:
volumes:
- 'storage:/srv' # required (for now not configurable)
- './database:/database' # optional if you want db to persist - configure a path under "database" dir in config file.
- './filebrowser.yaml:/filebrowser.yaml' # required
ports:
- '80:80'
image: gtstef/filebrowser
restart: always
volumes:
storage:
driver_opts:
type: cifs
o: "username=admin,password=password,rw" # enter valid info here
device: "//192.168.1.100/share/" # enter valid hinfo here
Not using docker (not recommended), download your binary from releases and run with your custom config file:
./filebrowser -c <filebrowser.yml or other /path/to/config.yaml>
All configuration is now done via a single configuration file:
filebrowser.yaml, here is an example of minimal configuration
file.
View the Configuration Help Page for available configuration options and other help.
If you currently use the original opensource filebrowser but want to try using this. I recommend you start fresh without reusing the database, but there are a few things you'll need to do if you must migrate:
- Create a configuration file as mentioned above.
- Copy your database file from the original filebrowser to the path of the new one.
- Update the configuration file to use the database (under server in filebrowser.yml)
- If you are using docker, update the docker-compose file or docker run command to use the config file as described in the install section above.
- If you are not using docker, just make sure you run filebrowser -c filebrowser.yml and have a valid filebrowser config.
The filebrowser Quantum application should run with the same user and rules that you have from the original. But keep in mind the differences that are mentioned at the top of this readme.
see Roadmap Page