nextcloud-in-docker-recipe VS SFTPGo

Here is configuration which i using to deploy my nextcloud https://github.com/MayMeow/nextcloud-in-docker-recipe

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.