Selfhosted

The weaker (permissive instead of copyleft) license alone is a reason to be suspicious of both the project and OP. At this point, it's just telegraphing plans to eventually go proprietary and enshittify.

Can't comment on the license, but I switched to it from NextCloud a few months ago and I've been generally very happy with it for where it is in the development process. It's not perfect yet, but it's also still earlyish.

I'm sorry - I understand it's free, but this is how I feel:

Nextcloud stopped being a fast, reliable file sync tool a long time ago (I mean - was it ever? it's free thats why most people use it).
It’s become a bloated “groupware suite” full of useless Talk, Groupware, AI, and half-finished apps…
while the core sync still chokes on large folders and locks files like it’s 2015.

The Core Problem PHP-FPM and mod_php are ancient architectures - every request spins up, runs, and dies. No persistent memory, no connection reuse, and no async I/O, no coroutines, slow as molasses non scalable backend held together only with redis.
Result: slow UI, slow sync, race conditions, and constant errors. Tons of open GitHub issues about sync bugs, upgrades, and no action from nextcloud. I'm sick of it. I'm done with it and I will be very direct about it.

Comments and issues and proposed classical PHP solutions are shocking:

https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html#configuring-your-web-server Nextcloud suggests you up its ram to 16Gb. 16Gb Carl!

php_value upload_max_filesize 16G
php_value post_max_size 16G

What about 17Gb files Nextcloud? nogo? don't use nextcloud then? Have you ever heard of TUS?

opencloud can run circles around nextcloud now - it is written in GO, much better architecturally, long running, uses connection pooling, does not need redis to survive.

What they (nextcloud) should do: Hyperf + Swoole
Swoole turns PHP into a high-performance async server - persistent memory, connection pooling, non-blocking I/O.
Hyperf+swoole - can rival GOlang. Hyperf builds on it: native WebSockets, coroutine HTTP, and microservice-ready architecture. You get live sync, push notifications, and massive concurrency with a fraction of the resource cost. Add TUS (resumable uploads) and you finally have reliable file transfer on bad connections.

I don’t want bloat. I want reliable sync that just works. I’d rather self-host a lean, fast sync app than manage ten half-integrated apps. They need to switch to Hyperf + Swoole - and bring Dropbox-level sync to self-hosting without the pain.

Nextcloud could fix its image by: Refocusing on sync reliability and performance. Moving core services to a persistent, async engine (Swoole / hyperf, etc). Making “Nextcloud Core” modular - separate entirely from the groupware/ai/talk - I don't fucking need it. Until then, those who care about speed, concurrency, and modern PHP should look beyond the old PHP-FPM world.

Im not the only person - people are sick of this inaction:

I really hate those posts with the "you should..." part. Let people use whatever they want.

I do something similar I use Pangolin (Which is an EXCELLENT project) as a self hosted alternative to cloudflareD tunels. I host it on a public VPS and then thru it tunnel web traffic to my public resources, that way I don't have to expose my IP or have a static. Then I also use netbird as an overlay network not only to access my servers remotely but also to "join" two sites via a VPN (Backup server at my mom's)

It needs to be running on postgres and redis. The AIO is your best bet

Nextcloud, tho a very capable package with just about all the bells and whistles one could ever need, is a resource eating beast. LOL

Probably language settings. Depending on your client you need to change those in the Lemmy WebUI. There's something like preferred languages.

Classic !languagesettings@lemmy.zip

You can absolutely use it without a reverse proxy. A proxy is just another fancy HTTP client that contacts the server on the original client's behalf and forwards the response back to it, usually wrapped in HTTPS. A man in the middle that you trust.

All you have to do is expose the desired port(s) to all addresses:

# ...
  - ports:
    - 8080:8080

...and obviously to set the URL environment variables to localhost or whatever address the server uses.

I'm not aware of an SFTP client that works like the cloud drive connectors. Do you know of one that monitors local files/dirs for changes and automatically sends them? Or polls the server for changes and downloads then (if they're on the allow list)? Keeps versions?

If literally all you're doing is occasional file transfers, sure, SFTP is easy. That's not how most people use cloud drive clients.

For me and my group, Nextcloud works fine and fast. We do more than file sync and share.