SaaSHub helps you find the best software and product alternatives Learn more →
Top 23 Filesystem Open-Source Projects
-
spacedrive
Spacedrive is an open source cross-platform file explorer, powered by a virtual distributed filesystem written in Rust.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
mountpoint-s3
A simple, high-throughput file client for mounting an Amazon S3 bucket as a local file system.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Project mention: Level Up Your Dev Workflow: Conquer Web Development with a Blazing Fast Neovim Setup (Part 1) | dev.to | 2024-03-16ripgrep: A super-fast file searcher. You can install it using your system's package manager (e.g., brew install ripgrep on macOS). fd: Another blazing-fast file finder. Installation instructions can be found here: https://github.com/sharkdp/fd
In the video, Mo talked about a few packages like Cidre and StrOm, and we referred to SpaceDrive.
If you want a file full browser experience choose nnn: https://github.com/jarun/nnn . If you have a desktop file for Helix you can use the Gnome Files program to make all your programming language files open in Helix.
Flysystem is a PHP project with open source code that revolutionizes work with the filesystem. It offers a unified and straightforward approach by abstracting the differences between various file system types, including local and cloud-based ones. You can utilize a consistent API to integrate it into your projects seamlessly. You can use it in any web application that works with data storage to make it more efficient and user-friendly.
Not sure these are really popular, but I cannot resist advertising a few utilities written in Go that I regularly use in my daily workflow:
- gdu: a NCDU clone, much faster on SSD mounts [1]
- duf: a `df` clone with a nicer interface [2]
- massren: a `vidir` clone (simpler to use but with fewer options) [3]
- gotop: a `top` clone [4]
- micro: a nice TUI editor [5]
Building this kind of tools in Go makes sense, as the executables are statically compiled and are thus easy to install on remote servers.
[1]: https://github.com/dundee/gdu
[2]: https://github.com/muesli/duf
[3]: https://github.com/laurent22/massren
[4]: https://github.com/xxxserxxx/gotop
[5]: https://github.com/zyedidia/micro
Project mention: The best testing setup for frontends, with Playwright and NextJS | dev.to | 2024-04-18For this, we'll use chokidar - more specifically the chokidar-cli package. chokidar is probably the most useful file watching library for the nodejs ecosystem and it will serve us well.
Project mention: South Korea's No.1 Search Engine Chose JuiceFS over Alluxio for AI Storage | dev.to | 2024-01-18Support for Kerberos keytab files
Project mention: What are some of the best libraries you cannot work without? | /r/node | 2023-06-08I haven't seen fs-extra mentioned yet. For my work it involves a fair bit of reading/writing to the filesystem, so this makes it quite nice to deal with everything in an async way.
The author needs to ask themselves: in this cloud technology stack, is there POSIX involved somewhere lower down, where I can't access it? The answer is, of course, "yes". The sort of cloud storage systems described all run on top of POSIX APIs. They provide convenience (cost efficiency is more debatable) compared to the POSIX alternative, but that's because they exist at an entirely different conceptual layer (hence the presence of POSIX anyway, just buried).
Your point about surfacing a POSIX that's actually there but hidden and thus visible to low-level Amazon employees building the S3 service which makes it invisible to S3 end customers is true but isn't the the point of the article. The author is saying there are motivations for a POSIX-like api visible also the end user.
So your explanation of stack looks like 2 layers: POSIX api <-- AWS S3 built on top of that
Author's essay is actually talking about 3 layers: POSIX <-- AWS S3 <-- POSIX
That's why the blog post has the following links to POSIX-on-top-of-S3-objects :
https://github.com/s3fs-fuse/s3fs-fuse
https://github.com/kahing/goofys
https://www.cuno.io/
And npmjs.com will block your IP if you do too many downloads in on day.
Actually is says 86m a week here: https://www.npmjs.com/package/rimraf
I fixed the problem, it was due to the incorrect setup of the google drive. I followed this guide to set everything up from scratch and create the folder directly in Linux instead of constantly accessing the apparently "encrypted" cloud. If anyone ever runs into the same problem, I really hope this thread is helpful :D
It's not really the same though. A Projected File System copies the files from the backing store to somewhere on the local file system when requested and then performs IO normally on the local files.
For an actual implementation of userspace filesystems on Windows see dokany: https://github.com/dokan-dev/dokany
The author needs to ask themselves: in this cloud technology stack, is there POSIX involved somewhere lower down, where I can't access it? The answer is, of course, "yes". The sort of cloud storage systems described all run on top of POSIX APIs. They provide convenience (cost efficiency is more debatable) compared to the POSIX alternative, but that's because they exist at an entirely different conceptual layer (hence the presence of POSIX anyway, just buried).
Your point about surfacing a POSIX that's actually there but hidden and thus visible to low-level Amazon employees building the S3 service which makes it invisible to S3 end customers is true but isn't the the point of the article. The author is saying there are motivations for a POSIX-like api visible also the end user.
So your explanation of stack looks like 2 layers: POSIX api <-- AWS S3 built on top of that
Author's essay is actually talking about 3 layers: POSIX <-- AWS S3 <-- POSIX
That's why the blog post has the following links to POSIX-on-top-of-S3-objects :
https://github.com/s3fs-fuse/s3fs-fuse
https://github.com/kahing/goofys
https://www.cuno.io/
Maybe https://github.com/itinance/react-native-fs would work? Or does TVOS even have a filesystem API?
Project mention: LittleFS Design (CObW) – Combining advantages of COW and log-structures | news.ycombinator.com | 2024-01-25
Project mention: Tell HN: ZFS silent data corruption bugfix – my research results | news.ycombinator.com | 2023-12-06https://github.com/gluster/glusterfs/issues/894
And apparently apart from modern coreutils using that, it is mostly gentoo users hitting the bugs in lseek.
... or does "S3 file system" mean https://github.com/awslabs/mountpoint-s3 - a Rust project by AWS Labs that provides "a simple, high-throughput file client for mounting an Amazon S3 bucket as a local file system" ?
Have a look at mergerfs.
Filesystem related posts
- Interview with Mo Rajabi, co-founder and CEO of Noor
- The best testing setup for frontends, with Playwright and NextJS
- OpenBSD 7.5 Released
- Row Zero and Viewport Data Streaming
- Autojump: A CD command that learns
- Simple Tape File System (STFS), a file system for tapes and tar files
- Show HN: Untree: like gron but generalised on indentation
-
A note from our sponsor - SaaSHub
www.saashub.com | 25 Apr 2024
Index
What are some of the best open-source Filesystem projects? This list will help you:
Project | Stars | |
---|---|---|
1 | fd | 31,581 |
2 | spacedrive | 28,841 |
3 | nnn | 18,170 |
4 | autojump | 15,929 |
5 | Flysystem | 13,193 |
6 | duf | 12,249 |
7 | chokidar | 10,542 |
8 | juicefs | 9,791 |
9 | fs-extra | 9,347 |
10 | s3fs-fuse | 8,065 |
11 | winfsp | 6,560 |
12 | rimraf | 5,484 |
13 | google-drive-ocamlfuse | 5,357 |
14 | dokany | 5,060 |
15 | goofys | 5,031 |
16 | react-native-fs | 4,875 |
17 | littlefs | 4,764 |
18 | GlusterFS | 4,478 |
19 | mountpoint-s3 | 4,003 |
20 | xplr | 3,928 |
21 | mergerfs | 3,868 |
22 | fselect | 3,803 |
23 | btfs | 3,809 |
Sponsored