New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Nextcloud AIO on Storage VPS with only 2GB of RAM?
Sup, I've been running a Seafile server instance alongside several small static websites (via nginx) and some podman containers (e.g. OpenWebUI) for quite some time now. Thinking about migrating from Seafile to Nextcloud AIO, but the official guide states the need for 4 gigs of RAM and 2 CPU cores.
Currently on a BuyVM VPS with only 2 gigs of RAM and a single vCore. Not really looking forward to migrating to the Storage VPS 1000 at 4x my current price, nor to migrating away. Does anyone here have experience if the VPS with its current specs can pull this off or is it a lost ordeal?
There's inconclusive discussions on the Nextcloud forums, so I thought I'd ask the trusty LET nerds for personal experiences. 
Comments
I've run several NC AIO instances and it's not likely going to be a great experience with 2g Ram and 1 core. You are definitely going to need to turn search and antivirus and any extra containers off. There's no way around that, I don't think. Good luck if you try though!
it worked like shit for me on 2gb ram
Any specific reason to migrate to Nextcloud from Seafile? I've tested both extensively and Nextcloud is significantly slower and less robust compared to Seafile.
In terms of 2 GB RAM, it would work well if you install Nextcloud manually, but no if you install the AIO through docker.
Thanks for the feedback. Main reason to consider switching came from the fact that the migration from my legacy Seafile instance to a containerized one hasn't been successful so far. The Nextcloud photos app also looks quite a bit more full-fledged and with the specs I've got right now, a deployment of e.g. Immich also doesn't seem viable.
Might want to stay with Seafile for now, then, and stay on the lookout for a beefier machine.
https://github.com/opencloud-eu
every considered opencloud?
https://docs.opencloud.eu/docs/admin/getting-started/container/docker-compose-local/
I would say stay on seafile
For foto apps, many people suggest immich.
I'm trying ente for now, so far it is good, although get some bad UX when migrating 550 GB files
Did you use traefik and minio?
I use storj for the s3 backend
The ente server is served using traefik and using docker compose
The database is served using coolify postgres + ssl for easier maintenance
So only ente selfhosted.
I haven't, and I wasn't aware of the project so far. Thanks for throwing that in.
Actually looks like a viable alternative. Lightweight, no enterprise / paid versions, and - most important for the described use case - a PosixFS driver for replicating the file tree on the disk exactly as stored in the libraries.
That would also allow for dedicated image library services, e.g. Immich, to read the files as @akhfa suggested. With Seafile's block storage, this is not really feasible as far as I can see.