I’ve setup Nectcloud but have done next to nothing with it.
My Lemmy instance gives me the most problems, but it’s also the only publicly available service I run. Mostly the issue is it seems to have a memory leak that forces me to restart it every few days.
Everything else has been completely rock solid for me, running on a mini pc (formerly a pi4 until I wanted to start doing stuff with Jellyfin and needed more power for transcoding) on OpenSUSE Leap all in docker containers. Makes it insanely easy to move stuff. I had no issues basically just copying the docker-compose files and data and bringing them up even when switching architectures.
gerowen@lemmy.world 10 months ago
I’ve hosted mine for years on my own bare metal Debian/Apache install and 28 is the first update that has been a major pain. I’ve had the occasional need to install a new package to enable a new feature, or needed to add new/missing insides up the database, but the web interface literally tells you how to do those things, so they’re not hard.
28 though broke several of the “featured” apps that I use regularly, like “Retention”. It also introduced some questionable UI changes that they had to fix with the recent .1 update. I’ll get occasional errors when trying to move or delete files in the web interface and everything. 28 really feels like beta software, even though we’re a point release in and I got it all from the “stable” update channel.
mhzawadi@lemmy.horwood.cloud 10 months ago
I’ve not moved to 28 yet, might wait a bit longer from your post. My 27 is rock solid, I don’t understand why so many have issues with nextcloud.
Maybe the docker installs are pants
gerowen@lemmy.world 10 months ago
I’m on my laptop so I thought I would elaborate on my first comment to give you things to watch out for if/when you update. I’ve been hosting mine with the zip file manually installed with my own Apache/PHP/MySQL/MariaDB setup for ages now without issue. It’s been rock solid except for, like I said, the occasional changes required to take advantage of new features such as adding new indices to the database or installing an additional php addon. Here’s the things that I noticed with updating to 28.
It seems like they’ve made some substantial under-the-hood changes to the user interface that shouldn’t have been shipped to the “stable” channel. It’s not completely broken, it “is” usable, especially after they restored my bulk move/copy button, but I still can’t use the Retention app, at least last time I looked, so I’ve literally got daily cron scripts to check those folders for old files and delete them, then trigger an occ files:scan of the affected directories to keep the Nextcloud database in sync with the changes. This however, bypasses the built-in trash bin so I can’t recover the files in the event of an issue. I actually considered rolling back to 27 for a bit, but decided against it, so if I were you, I would stick with 27 for a while and keep an ear to the ground regarding any issues people are having that are or aren’t getting fixed in 28.
unique_hemp@discuss.tchncs.de 10 months ago
I have run nextcloud:latest on Docker for the last 2 years and have had 0 problems. Maybe upgrading all the time works better than by releases.