I tried Nextcloud a while back and was not impressed - I had issues withe the speed of the Windows sync that were determined to be "normal" with no roadmap to getting fixed. I'm now planning to move off Windows desktop so that won't be an issue - so I thought I'd try again.
I went to nextcloud.com, clicked on Download-> Nextcloud server -> All-in-one -> Docker image - Setup AIO. This took me to the github README at Docker section. I'm already running docker for other things so I read the instructions, setup a new filesystem for my data directory and ran the suggested docker command with an appropriate "--env NEXTCLOUD_DATADIR=". I'm then left with a terminal running docker in the foreground - not a great way to run a background server but ok, I've been around for a while and can figure out how to make it autostart in the background ongoing. So I move on to the next step - open my browser at the appropriate URL and I'm presented with a simple page asking me to "Log in using your Nextcloud AIO passphrase:". I don't have a Nextcloud AIO passphrase and nothing I've read so far has mentioned it. When I search for it I get some results on how to reset it, but not much help. I could probably figure that out too, but after reading some more I found that Nextcloud requires a public hostname and can't work with a local name or IP address. I'm already running my home LAN with OpenVPN and access it from anywhere as "local" - I don't really want to create a new path into my home network just for Nextcloud.
I'm sorry - I know this sounds like a disgruntled rant and I guess it is. I just want to check that I'm not missing obvious things before I give up again. All I want is a simple file sync setup like onedrive but without the microsoft.
And here I am having used it for a decade and perfectly happy. I try other ones like Owncloud every once in a while and find them lacking. It was slow once upon a time but if you changed to postgres and used redis, it improved immensely. Today it's quite fast and the sync has been working great for a long time.
Use docker-compose with the AIO and it'll be a lot easier to manage. There's example compose files in the github repo.
Yeah, I can see how someone that has "grown up with it" could be happy. But as and experienced sysadmin coming at it for the first time - the documentation is a bit lacking.
Well, when I moved to the AIO, the documentation was plain wrong on several points. I submitted a bunch of changes that I had to do to make it work and they worked those changes in for the most part. Now it seems pretty workable, as a friend of mine used it to set his instance up and said it seemed to go fairly smoothly.