I’d like some advice on whether to install Nextcloud or Nextcloud All in One please.
I have recently started faffing around with a Raspberry Pi (never touched Linux before), learning as I go, making mistakes of course, and figuring things out.
I have a Raspberry Pi 4b (8GB) on which I have installed Docker and Portainer. I have used Portainer to add all containers in Docker.
The Pi has an SSD on one USB3 port, and HDD attached to the other via a powered USB3 hub. The SSD has the Pi OS, Docker and various containers.
I have recently installed Nextcloud, but in the process I discovered there is also All in One.
The HDD has data for Nextcloud users (no more than 4 users eventually).
So, may I ask what are the pro’s and con’s of Nextcloud and Nextcloud All in One please?
I’ve looked for a comparison, but haven’t found a clear enough explanation.
If there is one, please do signpost it.
The use case would be to not use any office type apps, but to mostly host photos.
Users will only ever access it on the home network.
Once set up, configured and running, I’d prefer it to have minimal intervention from myself.
Docker all in one, it should make it easy for people to deploy this rapidly and have a good working default configuration (and some selection of apps, …). You are in this docker-universe, then you probably have strategies, to use this to automatically create backups, deploy updates, …
I’m not sure about flexibilty, the snap packages had the problem that you could not modify them, I am not sure but that is probably different for the docker images.
From a performance point of view, you probably can get a better performance without these additional layers. However, you need to set it up on your own and do the configuration.
For the raspberry pi, there is also the NextcloudPi project, based on raspbian. It adds a few tools to the OS to handle some of the configuration stuff and helps to set up ssl certificates, doing backups, …
Give yourself time to learn about this. There is nothing wrong about testing Linux and different solutions with it, but expect things to go wrong in the beginning. Even if nowadays, things are set up prety easy, which is great, if you wanted to use it more seriously, I’d try to get some knowledge. E.g. on the raspberry pi, you often boot from the SD card, and you put the data on the external drive. Imagine, the SD card fails at some point, are you able to restore your setup with existing data on your drive?
Thank you @jtr and @tflidd
After having a look at the suggestions, I can see there is quite a buffet on offer
Sometimes, too much choice can be a bad thing, especially for us beginners.
But I’ll try things and learn along the way.
So I think I shall go the NextcloudPi route - but not in Docker, I’ll use another Pi I have for this.
I’ll document the steps I follow, and if it’s of interest, will post it up here (or wherever is the appropriate location).
In computer technology, you really only learn by trying out different things and then evaluating them for yourself.
Manual install, NextcloudPi, Nextcloud Docker or Nextcloud AIO? Why don’t you try out all the options and share your experiences with us? You will learn from these experiences and not from other people telling you the pros and cons of the solutions.
Thank you @devnull
Trying I am, as my wife reminds me
Too much choice, not enough time - so I’ve chosen NextcloudPi, and will share my experience…there may be a delay before I post, as I’m going into holiday/vacation time soon.
Remember that you are also practising for an emergency. You don’t want your Nextcloud to break at some point and not be able to repair it promptly. Then your wife will ask why you didn’t go for something reliable like Microsoft. In the cloud, you could also have Nextcloud hosted very reliably instead of Microsoft 365. Conversely, you cannot host Microsoft 365 at home.
Our documentation sucks, but hey, you are lucky, it is open source, so you can do it yourself
I was thinking that it would be really cool to have it and new users could benefit a lot from it. However, it is not easy to do, you’d need to know all the systems…
I’ve downloaded the latest NCP image for RPi4b, extracted it, used Balena Etcher to put it onto a spare 8GB microSD card.
Popped it into the Pi, powered up.
I kept a screen connected to the Pi, watched lots of text go scrolling past and have the last message to say NCP is not activated yet etc.
I can see from my router’s list of clients that nextcloudpi is on my home network, and it’s IP address.
Following the instructions to use my browser (Firefox) to open the activation page: https://ipaddress and https://nextcloudpi.local and https://nextcloudpi
all result in unable to connect.
I tried all as http:// as well.
I had the usual warning about secure site not available, but clicked continue to HTTP site, which reverted back to unable to connect.
Same result when using Brave browser.
Have I done something wrong? Am I missing something?
I’ve had an interesting afternoon going down many different routes on here and the internet to overcome this, and as @tflidd says, the documentation needs improvement, but I’m somewhat frustrated that I can’t even activate this thing.
I would post your query in a dedicated thread since it’s specific to the ncp install[1] if you hope to get anyone familiar with ncp to see your query and assist.
[1] Which is quite different from either of the Docker methods this thread was originally about).
