After I messed up my nextcloudpi installation, which had been running smoothly for years, by simply clicking an update button (see this thread), I am wondering how to avoid that going forward: I obviously need to keep the system up-to-date.
So my question: How much time is required to keep a nextcloudpi system up-to-date? How much time do you invest?
And what are best practices to do that with minimal effort?
Is it smarter to activate auto-updates for nc and ncp, and only intervene occasionally? Or do I need to schedule regular (monthly?) checks of my system to manually install updates?
How to handle major OS updates? For Debian, every 2nd year an LTS goes end of life.
For context: I am using nc on a RasPi 3b to only locally (within my LAN/wifi) synchronize contacts and calendars for 3 users, 7 or so devices. So a very lightweight task with 3 contact lists and 4 calendars. By only doing this locally, I see security requirements a little more relaxed than for an approach with external access - but staying up-to-date should definitely not hurt
For a small system like this I would say the most importand step ahead is:
backup, backup, backup
There is a lot of documentation like:
Autoupdate with a regular backup is a solution, yes. I prefer to see what happens and read the documentation ahead, but as you are relaxed with your system, this might work.
Cloning your system, checking the upgrade and rolling it out after success might make it a little more hassle-free as your production system keeps running. But there are too many factors to make any promises.
Addendum:
I saw now, Backup is already mentioned in your other thread. I’ll keep it here, as it can’t be emphasized enough.
I do not use NextcloudPi. Basically, you don’t necessarily have to use NextcloudPi on a Rasberry Pi. In the end, you have to choose between NextcloudPi, Snap, AIO, Docker, LAMP, … you are always stuck with something that might break after all. and the most important thing here is backup and restore and the correct backup, which you have also tested via restore. And even then, the upgrade path may no longer work at some point. No idea for what reason.
I usually use a pure LAMP installation without automatic scripts or Docker. But with Docker knowledge, Docker is also quite good. The less IT knowledge you have, the more you often have to rely on automated systems like NextcloudPi. But unfortunately you are then also dependent on it. And if it goes wrong, you will need a lot of time. Far more than the actual upgrades. Bear in mind that Nextcloud brings out a new release every four or six months or so.
that depends on how much time you have and how much time you’re willing to invest. you don’t have to use NextcloudPi just because you’re using a Raspberry Pi. there’s absolutely nothing wrong with using NextcloudPi, but you have the freedom to chose what is suitable for you. that’s FOSS.
generally if you’re using an SBC (single board computer) your goal is probably an IoT (Internet of Things) device which simply works without user interaction besides initial setup. The snap was designed with IoT in mind. there are very few requirements that need to be met.
If you are really only using Nextcloud to provide a backend for contacts and calendars for a few client devices, you might also want to consider something more lightweight and simple like Radicale, which could potentially make your life a lot easier as it has fewer dependencies to take care of than Nextcloud.
It’s also updated much less frequently, and when it is updated, it’s usually just bug fixes or security updates, so there are far fewer changes that have the potential to break your setup
