Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Filestash | 8,355 | 1 | a month ago | 4 | June 23, 2021 | 62 | agpl-3.0 | JavaScript | ||
🦄 A modern web client for SFTP, S3, FTP, WebDAV, Git, Minio, LDAP, CalDAV, CardDAV, Mysql, Backblaze, ... | ||||||||||
Davmail | 480 | 2 days ago | 160 | gpl-2.0 | Java | |||||
DavMail POP/IMAP/SMTP/Caldav/Carddav/LDAP Exchange and Office 365 Gateway - Synced with main subversion repository at | ||||||||||
Ccs Calendarserver | 363 | 4 years ago | 53 | apache-2.0 | Python | |||||
The Calendar and Contacts Server. | ||||||||||
Fennel.js | 221 | 1 | 2 | 7 months ago | 2 | February 10, 2014 | 2 | agpl-3.0 | JavaScript | |
Fennel.js is a proof of concept CardDAV / CalDAV server written in JavaScript. | ||||||||||
Php Push 2 | 65 | 10 years ago | 28 | agpl-3.0 | PHP | |||||
Z-Push Fork With CalDAV/LDAP Support | ||||||||||
Docker Davmail | 34 | 6 months ago | 2 | unlicense | Dockerfile | |||||
Docker container for DavMail POP/IMAP/SMTP/Caldav/Carddav/LDAP Exchange Gateway | ||||||||||
Calendar | 7 | 11 years ago | 5 | other | Oxygene | |||||
An open source CalDAV implementation for .NET and Mono, built on Data Abstract. | ||||||||||
Davmail Docker | 7 | 5 months ago | 3 | gpl-2.0 | Shell | |||||
Dockerfile for DavMail POP/IMAP/SMTP/Caldav/Carddav/LDAP Exchange Gateway | ||||||||||
Davmail | 6 | 3 years ago | mit | Dockerfile | ||||||
:skull: POP / IMAP / SMTP / Caldav / Carddav / LDAP Exchange Gateway | ||||||||||
Docker Davmail | 3 | 6 months ago | mit | Dockerfile | ||||||
DavMail POP/IMAP/SMTP/Caldav/Carddav/LDAP Exchange and Office 365 Gateway |
A Dropbox-like file manager that let you manage your data anywhere it is located:
FTP • FTPS • SFTP • WebDAV • Git • S3 • NFS • Samba • Artifactory • LDAP • Mysql
Storj • CardDAV • CalDAV • Backblaze B2 • Minio
Dropbox • Google Drive
;)
Filestash started as an attempt to solve the Dropbox problem by abstracting the storage aspect so you can "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
}
It has evolved with plugins which are the lego bricks you can assemble together to form a solution that works for you. You can bring your own identity provider, your own authorisation, your own search and more. If there's something you want, plugin will likely make it possible.
Some outside the box example of this "filesystem as a framework" ideas we've done for the sake of science:
3LX5KGmSmHDj5EuXrmUvcg77EJxCxmdsgW