Add s3 compatible storage

[eznix86]

Problem / Motivation

No s3 compatible storage yet.

Proposed Solution

Add one

Alternatives Considered

No response

Which part of Yerd?

Setup / installation

Additional Context

No response

[RichardAnderson]

Hey @eznix86, thanks so much for trying Yerd.

Whats the use case here for local S3 storage for local development? Surely for Laravel you can just use the local disk and switch configuration over to S3 for production? Otherwise, you could hook your local laravel site up to a cloud S3 storage provider - what benefit is a local S3 storage provider giving the general use? Sorry, just struggling to understand why someone would need this?

[eznix86]

Hi @RichardAnderson using local storage doesn't have pre-signed URLs, multipart uploads that I rely on instead of direct form upload. Also using S3 in both dev will helps avoid unpleasant surprises when deploying in prod.

[Thiritin]

Something simple and lightweight would be great here, i.e. something like Garage or SeweedFS. That just can run locally and dosen't take too much resources.

[Thiritin]

@RichardAnderson would you be okay if I make a integration for this and open a PR?

[RichardAnderson]

@Thiritin, sure. My plan was to use versitygw, as that seems to tick all the boxes, and supports MacOS, Linux and Windows, uses flat filesystems and is lightweight.

Rank	Framework	Pros	Cons
1	versitygw (chosen)	Stores objects as flat bucket/key files on disk (openable in Finder); single static Go binary; native macOS + Linux (amd64+arm64) prebuilt binaries; Apache-2.0; presigned URLs + multipart; loopback/rootless friendly; metadata in xattrs (APFS/ext4/xfs OK)	No first-class built-in web UI (optional/under-documented); xattr backend needs a normal local FS (not network mount / xattr-less tmpfs); SigV4 edge-case parity with real AWS SDKs must be verified; key-as-path sharp edge (foo vs foo/)
2	SeaweedFS	Built-in Admin UI (browse/upload/delete); single Go binary, all-in-one weed server -s3; native mac+linux binaries; Apache-2.0; presigned + multipart + versioning	Not flat on disk — objects packed into opaque .dat/.idx volume blobs + LevelDB metadata; S3 gateway hard-requires the filer (master+volume+filer+s3 quartet); classic Filer UI has no auth; some AWS error-path divergence; idle memory undocumented
3	Garage	Rust (matches our stack), lightweight, simple internals; single static binary, no external deps; presigned + multipart + CORS	No official macOS binaries (build from source); AGPLv3 (copyleft); not flat on disk (content-addressed blocks + embedded metadata DB); no built-in file browser; no object versioning / ACLs / bucket policies; one-time cluster-layout step
4	RustFS	Rust + Apache-2.0 (deliberately avoids AGPL); built-in console UI; ~30k stars, active; native mac (arm64) + linux	Too young to bundle — pre-1.0 beta, cluster of security advisories (Dec'25–Apr'26); opaque xl.meta storage (not flat); distributed durability "under testing"; no macOS x86_64 release; heavier multi-crate system
5	MinIO	Best-in-class S3 API compatibility; single Go binary; native mac+linux binaries; presigned + multipart	Community edition marked "NO LONGER MAINTAINED"; admin console gutted (May 2025, browser-only); opaque xl.meta storage (old flat FS mode removed); AGPLv3; RAM-hungry reputation; steered toward paid AIStor
6	gaul/s3proxy	Flat bucket/key files (filesystem-nio2 backend); Apache-2.0; presigned + multipart	Requires a JVM (no native binary); no web UI; xattr requirement bites on some filesystems; multipart ETag inconsistencies; limited ACL/versioning/policies — more dev/test than production
7	Zenko CloudServer	Full, production-grade S3 API; Apache-2.0; presigned + multipart	Runs on Node.js (no native binary); not flat on disk (split localData/localMetadata, opaque IDs); heavyweight; no first-party bucket browser in CloudServer itself; Docker/Node-oriented

I was planning these requirements;

Ability to...	CLI	GUI	Scope
Install the S3 (versitygw) service	✅ yerd service install	✅ Services view	v1
Start / stop / restart the service	✅ yerd service start|stop|restart	✅ Services view	v1
Change the versitygw version	✅ yerd service change-version	✅ Services view	v1
Enable / disable autostart on boot	✅ yerd service set-autostart	✅ Services view	v1
Set the service port	✅ yerd service set-port	✅ Services view	v1
Uninstall (optionally purge data)	✅ yerd service uninstall [--purge]	✅ Services view	v1
View service status (running / port / version)	✅ yerd services	✅ Services view	v1
List buckets	✅ yerd s3 buckets	✅ Buckets view	v1
Create a bucket	✅ yerd s3 create-bucket <name>	✅ Buckets view	v1
Delete a bucket	✅ yerd s3 drop-bucket <name>	✅ Buckets view	v1
View a bucket's object count + total size	✅ yerd s3 bucket-stats <name>	✅ Buckets view (lazy, on expand)	v1
View the S3 endpoint URL	✅ yerd s3 creds	✅ Credentials panel	v1
View / copy the access key	✅ yerd s3 creds	✅ Credentials panel (copy)	v1
Reveal / copy the secret key	✅ yerd s3 creds --show-secret	✅ Credentials panel (reveal + copy)	v1
Browse objects/files within a bucket	—	—	v2
Upload objects	—	—	v2
Download objects	—	—	v2
Delete individual objects	—	—	v2
Generate pre-signed URLs	—	—	v2
Rotate / regenerate credentials	—	—	future

The buckets view would be a sub-section under "Manage" like databases, but bigger - almost full screen.

[Thiritin]

@RichardAnderson could you look at the pr in Yerd-services, it adds the varsity gw, I added the cli commands and service for the Yerd app too. But to test that I need the PR #4 merged please!

[RichardAnderson]

@RichardAnderson could you look at the pr in Yerd-services, it adds the varsity gw, I added the cli commands and service for the Yerd app too. But to test that I need the PR #4 merged please!

Sorry about the delay, thats merged in and built.

[sineld]

+1 for RustFS