s3fs-fuse VS SFTPGo

The author needs to ask themselves: in this cloud technology stack, is there POSIX involved somewhere lower down, where I can't access it? The answer is, of course, "yes". The sort of cloud storage systems described all run on top of POSIX APIs. They provide convenience (cost efficiency is more debatable) compared to the POSIX alternative, but that's because they exist at an entirely different conceptual layer (hence the presence of POSIX anyway, just buried).

Your point about surfacing a POSIX that's actually there but hidden and thus visible to low-level Amazon employees building the S3 service which makes it invisible to S3 end customers is true but isn't the the point of the article. The author is saying there are motivations for a POSIX-like api visible also the end user.

So your explanation of stack looks like 2 layers: POSIX api <-- AWS S3 built on top of that

Author's essay is actually talking about 3 layers: POSIX <-- AWS S3 <-- POSIX

That's why the blog post has the following links to POSIX-on-top-of-S3-objects :

https://github.com/s3fs-fuse/s3fs-fuse

https://github.com/kahing/goofys

https://www.cuno.io/

sudo apt install build-essential libfuse-dev fuse git clone https://github.com/s3fs-fuse/s3fs-fuse.git cd s3fs-fuse sudo apt install libfuse2 sudo apt install libcurl4-openssl-dev sudo apt install libxml2-dev ./autogen.sh ./configure make

Don’t know actually. Here is project page.

s3fs-fuse

How is this different than these other solutions?

https://github.com/kahing/goofys

https://github.com/s3fs-fuse/s3fs-fuse

I don’t get it. Why not just improve https://github.com/s3fs-fuse/s3fs-fuse

EDIT: Thanks for the recommendations from all of you!! I've chose to use the below: - Files: sftpgo - Calendar: baikal - Notes: memos (But beware, it sends opt-out telemetry) - Network folder: webdav on sftpgo

Give a try to SFTPGo

> Even these projects have gotten to a level of sophistication that it would implode without big tech support.

The worst thing is that all this FAANG or VC backed companies make a lot of people believe that they are the only viable way.

> Why do you think you don't see any interesting oss tech from hobbyists is these days?

Actually not true, just an example, https://github.com/drakkan/sftpgo. But there are plenty of them.

This is possible using SFTPGo. The default Windows installer register SFTPGo as a Windows service. You can download the portable version and run it manually or install SFTPGo from the Scoop packages. You can use the built-in SFTPGo virtual permissions to only allow uploads. SFTPGo uses virtual users, no system users are required.

I suggest contacting your SFTP server vendor. I guess they have an auto blocking policy like this

Basically it's a file storage managed over HTTPS. Nextcloud is pretty heavy, that's the reason why I using just a single statically compiled cross-platform binary SFTPgo

Using SFTPGo you can easily configure read-only accounts. SFTPGo uses virtual users and virtual permissions. So you don't need to create system users for your SFTPGo users and you don't need to use chmod to make folders read-only (but the system user that SFTPGo runs as needs file system level permission to access the files/folders you want to share)

SFTPGo provides SFTP, FTP/S and HTTP/S so you can share the same files using different protocols and thus meet the different needs of your business partners. Allowed protocols can be enabled/disabled per-user

You could check out SFTPGo, it may meet your needs.