Features

• Manage your files from a browser
• Authentication middleware to connect to various source of user
• Flexible Share mechanism
• Chromecast support for images, music, and videos
• Video player
• Video transcoding (mov, mkv, avi, mpeg, and more)
• Image viewer
• Image transcoding (raw images from Nikon, Canon, and more)
• Photo management
• Audio player
• Shared links are full fledge network drive
• Office documents (docx, xlsx and more)
• Full org mode client (documentation)
• User friendly
• Mobile friendly
• Customisable
• Plugins
• Super fast
• Upload files and folders
• Download as zip
• Multiple cloud providers and protocols, easily extensible
• Nyan cat loader
• Emacs, VIM or Sublime keybindings ;)
• Pluggable Search (default is recursive search)
• .. and many more

Screenshots

Core Principles and Ideas

Filestash started as an attempt to solve the "Dropbox problem" by abstracting the storage layer, allowing you to "bring your own backend" by implementing this interface:

type IBackend interface {
	Init(params map[string]string, app *App) (IBackend, error) // constructor
	Ls(path string) ([]os.FileInfo, error)           // list files in a folder
	Cat(path string) (io.ReadCloser, error)          // download a file
	Mkdir(path string) error                         // create a folder
	Rm(path string) error                            // remove something
	Mv(from string, to string) error                 // rename something
	Save(path string, file io.Reader) error          // save a file
	Touch(path string) error                         // create a file
	LoginForm() Form                                 // dynamic form generation for the login
}

The software is effectively 2 distinct parts: Core and Plugins. Plugins act as "Lego blocks" that shape all the opinions on how the file manager operates, such as who can do what and where (aka, the authorisation), how the search features work (e.g., recursive search, full text search, ...), how users are authenticated (e.g., passthrough to the storage layer, LDAP, OIDC, SAML, signed URLs), how the application behaves when opening different file types, etc...

The architecture is designed to enable implementers to build file managers that are fit for purpose. To cite an example, several control panels for elevators in Europe feature QR codes generated by Filestash. Technicians responsible for their maintenance scan these QR codes to access the complete history of the elevator, upload new records, access relevant external resources, and view a banner displaying location specific metadata from the ERP. What would have been a complex custom solution was made possible through the addition of two plugins: one for QR code generation and another for ERP integration. Everything else was off the shelf.

Documentation

• Getting started
• Installation
• API

Support

• For companies -> support contract
• For individuals -> #filestash on IRC (libera.chat). To financially contribute to the project:
  • Bitcoin: 3LX5KGmSmHDj5EuXrmUvcg77EJxCxmdsgW
  • Open Collective

Credits

• Contributors and folks developing awesome libraries
• This project is tested with BrowserStack
• Logo derived from the work of ssnjrthegr8, Iconography from flaticon, fontawesome and material
• libvips and libraw. Those libraries are statically compiled in Filestash. Instructions to build Filestash is available here and instructions to create your own static library for libvips and libraw is to be found here