jamhall/s3rver

Project maintenance status

kherock opened this issue · 0 comments

Hi all!

This project is currently lacking an active lead maintainer. I no longer have an active use case for local S3 development and do not have the time to keep this library up-to-date with a level of quality I'd be happy with.

In its current state, this project is already pretty useful and handles many of S3's edge cases with grace. Though with the deprecation of Node 8, AWS Signature Version 2, and path-style bucket access, it's embarrassingly fallen a bit behind and isn't an accessible way for developers to create S3 test environments right now.

Current v4.x plans:

  • Drop support for Node 8, 10 #638
  • Implement complete AWS Signature Version 4 verification #534
  • More accessible simulation of subdomain and vhost-style buckets (since path-style buckets are going away Fall 2020) #635
  • Support creating buckets without Signature Version 2 support**
  • Support creating buckets without path-style access**
  • More useful documentation #640
    • complete example configurations/projects for common use-cases
    • feature table documenting the supported S3 API surface
  • more useful logging output (suggestions welcome)

** AWS doesn't yet document how buckets will behave once these restrictions are in place, initial support will be experimental

My v4.x wishlist (v4.1 and beyond)

  • hooking up S3 events to an SQS API, i.e. ElasticMQ
  • official Docker image #624
  • Object versioning #7
  • alternative storage backend supporting S3 select #230