Back
gh

mickael-kerjean/filestash: :file_folder: File Management Platform / Universal Data Access Layer (without FUSE)

:file_folder: File Management Platform / Universal Data Access Layer (without FUSE) - mickael-kerjean/filestash

by mickael-kerjean github.com 933 words
View original

screenshot

What is this?

It started as a storage agnostic Dropbox-like file manager that works with every storage protocol: FTP, SFTP, S3, SMB, WebDAV, IPFS, and about 20 more.

It grew into what we want to be the world’s best file management platform, where everything that’s not a fundamental truth of the universe lives in a plugin. Where other platforms are take-it-or-leave-it, ours gives you a rock solid core and a plugin system to handle opinions, so however deep requirements go, the only limit won’t be technical but your own creativity.

storage + auth architecture

Key Features

Getting Started

To install Filestash, head to the Getting started guide. If you want to leverage plugins, head over to the inventory, or learn about developing your own plugins.

If you want guidance and expert help on your file management problem, book a call and let’s figure out if Filestash is the right platform for you.

Vision & Philosophy

Our goal is simple: to build the best file management platform ever made. Period. But “best” means different things to different people, and making Filestash modular is the only sane model to accomplish that. Anything that isn’t a fundamental truth of the universe and might spark a debate belongs in a plugin. Literally every piece listed in the key features is a plugin you can swap for another implementation or remove entirely.

This modularity is made possible by the magic of programming interfaces. For example, if you want a Dropbox-like frontend for FTP, you will find out the FTP plugin simply implements this interface:

type IBackend interface {
    Ls(path string) ([]os.FileInfo, error)           // list files in a folder
    Stat(path string) (os.FileInfo, error)           // file stat
    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

    // I have omitted 2 other methods, a first one to enable connections reuse and
    // another one to declare what should the login form be like.
}

There are interfaces you can implement for every key component of Filestash: from storage, to authentication, authorisation, custom apps, search, thumbnailing, frontend patches, middleware, endpoint creation and a few others documented in the plugin development guide.

To see what’s currently installed in your instance, head over to /about. The inventory of plugins is documented here

Support

Credits

Filestash stands on the shoulder of: contributors, folks developing awesome libraries, a whole bunch of C stuff (the C standard library, libjpeg, libpng, libgif, libraw and many more), fontawesome, material, Browser stack to let us test on real devices, and the many guys from Nebraska and elsewhere who have been thanklessly maintaining the critical pieces that Filestash sits on top:

credit to the nebraska guy on xkcd