A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
- Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
- No spam posting.
- Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
- Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
- No trolling.
Resources:
> Any issues on the community? Report it using the report flag.
> Questions? DM the mods!
- 1 user online
- 218 users / day
- 9 users / week
- 244 users / month
- 841 users / 6 months
- 0 subscribers
- 542 Posts
- 8.93K Comments
- Modlog
Love MinIO but it’s not a filesystem and mounting object storage as a filesystem is not a great experience (speaking from commercial experience).
Same experience here. S3 is essentially a key/value store to simply put and retrieve large values/blobs. Everything resembling filesystem features is just convention over how keys are named. Comminication uses HTTP, so there is a lot of overhead when working with it as an FS.
In the web you can use these properties to your advantage: you can talk to S3 with simple HTTP clients, you can use reverse proxies, you can put a CDN in front and have a static file server.
But FS utils are almost always optimized for instant block based access and fast metadata responses. Something simple like a
find
will fuck you over with S3.