= NextCloud AIO vs. NextCloud Bare Metal =

I've been running various forms of NextCloud over the last two years. This is strictly for personal use at home on my Odroid HC4 (an ARM board similar to RPi). I started with NextCloudPi installed, but then I moved to a bare metal installation as I wanted to try out an update before it was packaged for NextCloudPi

My biggest priority in setting this up is that I have a good backup strategy. On NextCloudPi, the ability to backup and recover a full instance, including or excluding data, was built right into the package. I loved this feature. On the bare metal installation, I had to schedule a cron job to backup the config file, the database, and the files to a compressed
.tar.gz. I was never certain how restoring this was going to work though, and thankfully I attempted this yesterday to ensure that my backups were appropriate; they were not. I built a new box from scratch, installed NC with Apache + PHP (which isn't entirely intuitive with the various versions of PHP compatibility with NextCloud), and recovered the config files, database, and data files. I ended up with a myriad of errors that didn't appear to be working. I'm getting close to the point where I just want a working solution - I don't want to be investing hours into getting something complex working

Enter NextCloud AIO, a Docker container meant to replicate something close to what NextCloudPi offered. This was relatively straightforward to setup once I got it working

**Do I have to be worried about future development of NextCloud AIO I was able to perform a backup (and I'm amidst testing a recovery to make sure those backups work) through the "Borg" backup utility provided with NextCloud AIO, but my worry with these pre-packaged solutions is always long-term maintenance. In the case of NextCloudPi, as we've seen, the maintainer has stepped away from the project. Had I not been paying attention and was blindly still running this and taking regular backups, I'd likely bewith ever recovering my data. With a bare metal installation, this is never a worry has you have all of the components (files, configuration, database) separately and can always integrate those into a future implementation of NextCloud. Now that I've sought, again, a simpler pre-packaged solution, I wonder if I should be worried about future development of AIO


Based on what docker containers are running after installing NextCloud AIO, I would assume similar performance. AIO seems to simply be a utility to simplify and containerized each individual component of NextCloud. For example, here is what is running on my box that is only serving NextCloud:
aio-apache
aio-nextcloud
aio-redis
aio-postgresql
aio-borgbackup
aio-domaincheck
aio-mastercontainer
EDIT: More memory usage so far. With bare metal, I was seeing anywhere from 1-1.5GB of memory usage from idle to load. Over the last ten minutes, it's so far ranged from 1.5-2.4GB

I prefer using Docker for management of PHP versions and extensions, plus isolation; and hosting NextCloud as an usual PHP app inside that container

This gives best balance between control and flexibility. Your data lays straight in a folder of your choice, next to NextCloud wwwroot. Your DB data files are directly available as well. Add a couple of scripts and a cron job for backup and you are all set

As for redis etc - I simply don’t need it for small-scale setups (1-2 users)

As for AIO and other variants - I simply do not trust them (in terms of architecture). I know my docker-compose solution, and I’m sure that I will be able to fix any issues, if any arise. Cannot say the same about those ‘good-for-everyone’ solutions

It’s very good that you actually check whether you can restore data from your backups. However, I believe that setting DB + files backup shouldn’t be very difficult. We all make mistakes, but once they are fixed, the backup process shouldn’t be that complicated so you would have to switch something other

== About Community ==
Members
Online