or rclone serve
If we're just talking verifying S3 connectivity, simply spinning up "rclone serve s3" appears to be the simplest solution.
21–30 of 112 posts
or rclone serve
If we're just talking verifying S3 connectivity, simply spinning up "rclone serve s3" appears to be the simplest solution.
Just use the damn file system. Why does everyone have to put HTTP between everything?
This is what I went with.
I use it in end to end tests as an S3 simulator that starts and stops instantly and reads & writes to a local directory, - as you'd expect it's great in that role. No complaints. Given the fork's maintainer puts their real name on it & stakes their reputation, you'd assume it can be trusted - but my use case is simpler than most.
I use JuiceFS https://github.com/juicedata/juicefs if you think the Chinese are worth the trust
I use JuiceFS https://github.com/juicedata/juicefs if you think the Chinese are worth the trust
If it's open source, you don't do daily pulls and you have a competent AI to crawl the codebase; why does it matter the ethnicity at this point?
Incus (spiritual successor to LXD, after the fork-off by Canonical) has a simple S3 server built-in.
A notable mention should also be Versity GW, https://github.com/versity/versitygw/
Also discussions few months ago here when healthcheks.io switched to it: https://news.ycombinator.com/item?id=47806348
A notable mention should also be Versity GW, https://github.com/versity/versitygw/