←back to thread

S3 as a Git remote and LFS server

(github.com)
194 points kbumsik | 3 comments | 19 Oct 24 10:37 UTC | HN request time: 0.41s | source
Show context
mdaniel ◴[19 Oct 24 17:20 UTC] No.41889095[source]▶
All this mocking when moto exists is just :-( https://github.com/awslabs/git-remote-s3/blob/v0.1.19/test/r...

Actually, moto is just one bandaid for that problem - there are SO MANY s3 storage implementations, including the pre-license-switch Apache 2 version of minio (one need not use a bleeding edge for something as relatively stable as the S3 Api)

replies(3): >>41889194 #>>41889525 #>>41896008 #
notpushkin ◴[19 Oct 24 18:17 UTC] No.41889525[source]▶
> there are SO MANY s3 storage implementations

I suppose given this is under the AWS Labs org, they don’t really care about non-AWS S3 implementations.

replies(1): >>41889981 #
1. mdaniel ◴[19 Oct 24 19:18 UTC] No.41889981[source]▶
Well, I look forward to their `docker run awslabs/the-real-s3:latest` implementation then. Until such time, monkeypatching api calls to always give the exact answer the consumer is looking for is damn cheating
replies(2): >>41890151 #>>41890250 #
2. chrsig ◴[19 Oct 24 19:38 UTC] No.41890151[source]▶
it wouldn't be unprecedented. dynamodb-local exists.
3. notpushkin ◴[19 Oct 24 19:51 UTC] No.41890250[source]▶
Agreed, haha. Well, I think it should work with Minio & co. just as well, but be prepared to have your issues closed as unsupported. (Pesonally, I might give it a go with Backblaze B2 just to play around, yeah)