40b0cd4b66
Former-commit-id: a68e501a962cdd7c3a9e5a3d91433cbec34265e3 [formerly ab4763c975794e5997fab6abb51b2e91bda6e08a] [formerly 709e134df8986005308f3e125348fe13cf92919a [formerly
|
||
|---|---|---|
| .circleci | ||
| .github/ISSUE_TEMPLATE | ||
| bolt | ||
| build | ||
| caddy | ||
| cmd/filebrowser | ||
| dockerfiles | ||
| frontend@f5c48c9679 | ||
| http | ||
| staticgen | ||
| .dockerignore | ||
| .gitignore | ||
| .gitmodules | ||
| .goreleaser.yml | ||
| .travis.yml | ||
| doc.go | ||
| Docker.json | ||
| file.go | ||
| filebrowser.go | ||
| Gopkg.lock | ||
| Gopkg.toml | ||
| LICENSE | ||
| publish.sh | ||
| README.md | ||
| rice-box.go.REMOVED.git-id | ||
In Q2 2018, this project was renamed from filemanager to filebrowser, a new GitHub organization was created and the main repo was moved from hacdias/filemanager to filebrowser/filebrowser. Old refs will work, because permanent redirects are set up. However, we suggest every contributor to update the remote URLs in their local clones. See Changing a remote's URL.
Moreover, the previously unique repo was split into multiple pieces: frontend, logo, caddy... At the same time, the official docker image was changed to hacdias/filebrowser. Users are encouraged to check their sources and update them accordingly.
filebrowser
filebrowser provides a file managing interface within a specified directory and it 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 own directory. It can be used as a standalone app or as a middleware.
Table of contents
Getting started
You can find the Getting Started guide on the documentation.
Features
Easy login system.
Listings of your files, available in two styles: mosaic and list. You can delete, move, rename, upload and create new files, as well as directories. Single files can be downloaded directly, and multiple files as .zip, .tar, .tar.gz, .tar.bz2 or .tar.xz.
File Browser editor is powered by Codemirror and if you're working with markdown files with metadata, both parts will be separated from each other so you can focus on the content.
On the settings page, a regular user can set its own custom CSS to personalize the experience and change its password. For admins, they can manage the permissions of each user, set commands which can be executed when certain events are triggered (such as before saving and after saving) and change plugin's settings.
We also allow the users to search in the directories and execute commands if allowed.
Users
We support multiple users and each user can have its own scope and custom stylesheet. The administrator is able to choose which permissions should be given to the users, as well as the commands they can execute. Each user also have a set of rules, in which he can be prevented or allowed to access some directories (regular expressions included!).
Search
File Browser allows you to search through your files and it has some options. By default, your search will be something like this:
this are keywords
If you search for that it will look at every file that contains "this", "are" or "keywords" on their name. If you want to search for an exact term, you should surround your search by double quotes:
"this is the name"
That will search for any file that contains "this is the name" on its name. It won't search for each separated term this time.
By default, every search will be case insensitive. Although, you can make a case sensitive search by adding case:sensitive to the search terms, like this:
this are keywords case:sensitive
Contributing
The contributing guidelines can be found here.