No longer active?

[xeoneox]

Is this project no longer active?

That would be a shame as self hosting S3 is getting a lot of attention right now.

in addition we have, https://github.com/poundifdef/smoothmq

All the pieces are there waiting to be assembled. What can be done to help revive this project?

[sebsto]

Well, this capability is now offered natively by S3. There is no need for this open source project anymore.

https://docs.aws.amazon.com/AmazonS3/latest/userguide/mountpoint.html

The source code is available here

https://github.com/awslabs/mountpoint-s3

[jazzl0ver]

@sebsto unfortunately, the mountpoint-s3 projects still lacks support of commonly used operations like (unlike yas3fs):

but probably not the right fit for applications that:
use file operations that S3 doesn't natively support, like directory renaming or symlinks
make edits to existing files (don't work on your Git repository or run vim in Mountpoint 😄)

[jazzl0ver]

@xeoneox feel free to publish a pull request. unfortunately, i have no time and need to improve the current implementation

[xeoneox]

Well, this capability is now offered natively by S3. There is no need for this open source project anymore.

https://docs.aws.amazon.com/AmazonS3/latest/userguide/mountpoint.html

The source code is available here

https://github.com/awslabs/mountpoint-s3

Mountpoint-s3 does not solve the chatter problem between multiple clients. It's very nice, but it does not address the underlying features yas3fs solves. I also had a few issues running mountpoint-s3 under my minimal Kubernetes OS base, but luckily GeeseFS is pretty close feature-wise with less restrictions on my host. Right now, I solve this server side, Geese for simple operations, and a distributed filesystem on top of s3 using JuiceFS when I need something with full Posix compliance and network locking. Handling write fencing client side could be so much nicer though, and maintains the simplicity.

Yas3fs is a very clean, bolt on solution that keeps the server side minimal. It's a shame to see it die

[jazzl0ver]

@xeoneox

Yas3fs is a very clean, bolt on solution that keeps the server side minimal. It's a shame to see it die

just wondering, what exactly is missing in yas3fs at the moment?

[xeoneox]

For me, smoothmq, or especially Kafka support, would be a game changer

[jazzl0ver]

looks like implementing smoothmq will require migration to boto3.sqs, which is possible (especially with an AI help) but not a demand for me.
kafka is not sqs-compatible, so it will require much more efforts. but - again - i don't really need it at the moment, sorry.

if you have time and skills, feel free to implement it and i'll be happy to merge your PR.