I’m currently running an old Synology DS218+, which is now old enough to that I can’t even get the version of php that Nextcloud needs. While I’ve built a TrueNAS scale, I’m debating whether it’s worth looking at Nextcloud as a managed hosted service, vs running it locally.
The last time I tried it was a good few years back, and Nextcloud was clunky as heck and slow. What’s the current state of play for self-hosting it?
Depends for one on the amount of users you expect to serve.
I’m hosting nextcloud on an rpi4 4gb, mariadb, APCu, imaginary and serving 3 family members. That’s running smoothly, even though the rpi is also running a VPN server, NFS server and paperless ngx.
I’m not yet using nextcloud mail though.
Thanks, that’s good to know. Given this is solo access, looks like an RPi may be a good choice!
I believe nextcloud aio with Docker is all the rage nowadays because it is so easy to set up.
No experience myself. I started bare metal on an rpi2b+ IIRC when the world was a bit younger and still Dockerless and ported that install first to a rpi3 and then to the rpi4.
Thanks, I tried AIO but sadly by DS218+ is out of date for PHP and won’t allow any further updates. Absolutely dumping Synology based on that stance.
Setting up a memcache and imaginary (for preview generation) were 2 important optimizations for my use case, butc even before i did that things worked well.
Well I think I can wrap this one up 
. NextCloud is using a 32bit integer for calendaring, which means it’s impossible to view, edit or add entries after 2037, so all my pension and mortgage planning dates are effectively useless. This also applies to all web-hosting orgs who use NextCloud as their backend, including Proton. 
I would never have even thought about looking into this kind of constraint.
Good find!