Love me some docker compose! I switched from a manually built VM over to the AIO setup about a year ago and never looked back. It’s been rock solid for me and my ~10 users so far.
I appreciate the simplicity, but giving such broad permissions makes me unease and the main reason why I’m putting off moving to Nextcloud AIO. Am I the only one who thinks like this?
It containerizes all the subcomponents under a mastercontainer, and even has support for community containers of things like pihole, caddy and dlna. So you have image control over each component, as well as codespace separation.
After 7 or 8 years of various forms of Nextcloud, I have to say this is the easiest one to maintain, upgrade and backup outside of my VM snapshots.
Not really, it just makes containers in your docker, accessible like any others. The mastercontainer can be used to control and update them, but you can just exec -dit them like any other containers you find in your docker ps
I could never get the AIO setup to work well for some reason. It was also a couple versions behind it seemed.
I…uh…know it’s not popular on the fed, but I use the nextcloud snap package and it’s been rock solid. It’s always up -to-date and they have a backup/export feature too.
People talk a lot of smack on snap, but installed the nextcloud snap 5 years ago to check out nextcloud and see if I liked it. I did, and the snap was so easy that it stuck around for 5 years. I didn’t do anything except update the underlying OS. It is really well maintained.
I just migrated off of it to get a little more flexability, but I have nothing but good things to say about it.
I couldn’t make things easy for myself when I migrated, because I wanted to use postgres, while the snap uses mysql/mariadb and I wanted S3 storage instead of file system.
In the end I just pulled down all the user filed and exported the calendars and contacts manually, then imported them on the new instance.
There are some blog posts on migrating db types, but my install is very minimal and I just didn’t want the headache.
If you don’t want to change the database type, then you can just dump the db from the snap, backup the user file directory, then restore into the new database and rsync up all the files.
I was about to ask why this is better than the docker installation, but I see step one is to install docker haha.
I’ve been running the docker container for a long time, it works very well. It is a bit more complicated if you try and use extensions that require seperatw containers (like setting up collabora), but that can be done as well. It’s just more complicated.
I do remember needing to know how to access the internal terminal a few times, but I don’t remember why. If I think of it I’ll come back and add instructions.
As a former self-configured docker compose NC user, I have to say I’m way happier with the AIO. But still, the older docker method was head and shoulders over any other method of running NC that I’d used.
I’m still using the self hosted docker image, the all in one is too bloated for me and my computing resources are quite limited. Why would I like an antivirus? Or a backup solution different than the one I use to backup the rest of my containers?
Cool initiative anyway for other kind of users though.
I wish I could’ve like next cloud more, but it seemed bloated as all hell and was slow regardless of what machine I tried running it on :(. I might give it another go one day.
One of the first services on my server was nextcloud in docker container from lsio. Never had problems so there was no need to try AIO, but so many people recommend that, it will be my next setup if this one fails me
I decided to go with this one because it’s now the official distribution channel and supported by the devs. But the lsio one looks pretty solid as well.
As in, I have Nginx running on my server and use it as a reverse proxy to access a variety of apps and services. But can’t get it playing nicely with AIO Nextcloud.
Add comment