Nextcloud by a mile. That’s where the primary devs from Owncloud went, consequently all new work has been done there. As well, Owncloud got sold to some shitbird corporate suite just recently, it’ll be dead in a year.
Use the AIO docker image, preferably on a VM docker host you can snapshot.
Just some tips when using nextcloud official docker container. Do not use the ‘latest’ tag. Instead, use the version tag (e.g. “27-apache”). This is to prevent breaking your install when you accidentally upgrading between major versions that way too far apart (say, v23 to v27).
When upgrading nextcloud containers, always upgrade one major version at a time. For example, if you’re currently in v25 and want to upgrade to v27, upgrade to v26 first before upgrading to v27. Not sure if nextcloud already added some safeguard for this, but this issue often bites new nextcloud selfhosters in the past.
Yeah my data is still missing
It only affected files I created on drive via the web for me so their explanation doesn’t even apply to me
Screw this I’m actually going to finish setting up my own cloud service because fuck this
Now the question is OwnCloud or NextCloud?
Nextcloud by a mile. That’s where the primary devs from Owncloud went, consequently all new work has been done there. As well, Owncloud got sold to some shitbird corporate suite just recently, it’ll be dead in a year.
Use the AIO docker image, preferably on a VM docker host you can snapshot.
NextCloud it is then
I’ve currently got an overkill system running TrueNAS Scale so I’ll be using the docker image for sure
Just some tips when using nextcloud official docker container. Do not use the ‘latest’ tag. Instead, use the version tag (e.g. “27-apache”). This is to prevent breaking your install when you accidentally upgrading between major versions that way too far apart (say, v23 to v27).
When upgrading nextcloud containers, always upgrade one major version at a time. For example, if you’re currently in v25 and want to upgrade to v27, upgrade to v26 first before upgrading to v27. Not sure if nextcloud already added some safeguard for this, but this issue often bites new nextcloud selfhosters in the past.