I am wanting to start to self host my own NextCloud instance on a Pi.
I have dabbled with it on my Linux server but the fact is that it really does suck too much juice from the wall even when I have set everything in BIOS to low power mode.
I don’t want to spend any more money on parts and I have a number of Pi’s lying around doing nothing.
I am comfortable with Linux and in the CLI so that isn’t an issue for me - But I know nothing about redundancy, high availability or kubernetes.
My goal here, is to have a stack of 3 Pi’s, with 1 external drive attached to 1 of the Pi’s - If one of the Pi’s were to crash/die, that the NextCloud instance would not be affected and the user would be none the wiser that one Pi has failed.
I don’t even know where to start with this, so any guidance is much appreciated.
Should be pretty straightforward.
Create a Gluster cluster for the Nextcloud application and data files. Next you can create a master-master database cluster with MariaDB and Galera. This will allow any single pi to fail and maintain quorum to keep Nextcloud online.
You may want to create symbolic links from within the Galera share to common configuration files, stuff like a php.ini or nginx.conf. That is up to you though, and you would still need to restart the services manually.
Definitely jump in and see how far you get. If you have any issues definitely report back!
2 Likes
What I’d do first before following the excellent suggestions given by judahnator is spin up a Nextcloud istance on a Pi 3 and see if it’s speedy enough for you.
I have my current Nextcloud istance on a Docker container (which is also way easier to deploy rather than going with a manual installation) on a Pi 4 @2GHz and I’d say it’s usable. Not a speed demon but it’s also not gonna let you hang for a while. The same could not be said for the installation I tried on a Pi 2. The 3 is faster, but that 1GB of RAM and the “gigabit” through USB are gonna limit the performance by quite a lot.
2 Likes