Hi everyone,

I’m seriously thinking about moving from Nextcloud AIO to OwnCloud Infinite Scale (OCIS), and I’d love to hear your thoughts.

Here’s why I’m considering the switch:

  1. I need software that’s stable and doesn’t break after every update.
  2. Minimal maintenance is a priority for me.
  3. A solution that works out of the box with minimal setup complexity.
  4. Support for Docker Compose deployment.
  5. Support for S3 storage as the primary storage backend.

What I like about OCIS:

  1. It’s written in Go (which I prefer over PHP).
  2. It doesn’t require a database, simplifying setup and maintenance. (Not sure about it)

However, I’m still hesitant due to:

  1. The limited documentation for OCIS.
  2. Concerns about whether it’s as open-source friendly as Nextcloud.

While I’ve been using Nextcloud Talk, I find it slow and unstable, so I’m planning to transition to XMPP. That said, Nextcloud itself has been challenging to maintain, and I’m looking for something faster and more reliable.

For those who have experience with OCIS, would you recommend switching, or should I stick with Nextcloud despite its issues?

Thanks in advance for your input!

16 points

Nextcloud Docker compose https://hub.docker.com/_/nextcloud/

I don’t do much maintenance on my nextcloud image either. I spend a lot of time setting it up on bare metal because I didn’t know docker compose existed but it’s very popular nowadays. With docker compose you don’t have to setup a lot either. It didn’t break for me once in the past years.

What’s wrong with nextcloud’s S3 object storage?

permalink
report
reply
2 points

I used NextCloud in a Docker container but found that unless I was really on top of checking versions for updates, it was very easy to get behind and then unless one way VERY careful about going up in the correct increments, it was quite easy to end up with a version mismatch between the files and DB structure.

As much as I hate SNAP (mainly due to them being overused on Ubuntu desktop and bloaty blobs full of weird permission issues) I’ve got to say that moving to a SNAP version of NextCloud on my server has made my life so much easier. A scheduled job runs a “snap refresh” regularly and it’s been fairly stable for over a year now, except for one small incident where it broke the reference to the internal office suite install and for some reason stated trying to go with a localhost version

permalink
report
parent
reply
2 points

Podman has a built-in automatic update feature that monitors the source repo. Could be useful for you.

permalink
report
parent
reply
2 points

I use Nextcloud AIO. If you use s3 as primary storage, the backup (using Borgbackup) won’t work.

https://github.com/nextcloud/all-in-one

permalink
report
parent
reply
5 points

I started and ended up bailing. The deciding factor for me was the way data is stored with OCIS (basically hashes), so backup/restore would be a much larger pain. So I’m sticking with Nextcloud as much as I hate PHP and dislike the performance issues.

permalink
report
reply
1 point

I thought backup/restore would be easier with OCIS 🤔

permalink
report
parent
reply
3 points

Here’s how I think about it. If my NAS goes down and I need a specific file from backup, how would I get that? With OCIS, everything is stored with a hash, whereas with Nextcloud it’s stored by filename. So to me, Nextcloud seems easier to deal with.

permalink
report
parent
reply
4 points

Just to throw my own experience in the mix. I tried the AIO and standard versions of Nextcloud and found them to be flakey and slow. But I felt compelled to keep trying. That’s when I found NextcloudPi. I’ve installed it on a Pi4 running from an external SSD and it’s been rock solid. I believe that version is no longer in development though and I primarily use it as a sync platform for various apps rather than using the web apps directly.

And just to be contrary, have you looked at Seafile? It’s stupid fast and stable but some features are hidden behind a paywall if you have more than 3 users (community vs pro). Their documentation is poor, and the data is stored in Git-lik chunks on the server. All of which can be a deal breaker for some. The external storage feature works, but for a newb like me, it was a bear to get running.

permalink
report
reply
2 points

I had good and bad times with both. I am finally happy with “pydio cells”

permalink
report
reply
1 point

What issues did you face with OCIS?

permalink
report
parent
reply
2 points

First, nothing. But I run just my private containers and update them automatically with watchtower. I like it when I could don’t care about things. OCIS was one of the freaky ones. Breaking changes are literally breaking everything. I lose the data and start over two or three times. (The data wasn’t completely lost, I had backups and/or was able to use an older version instead.)

permalink
report
parent
reply
1 point

The issue you faced is clearly a scary one!

permalink
report
parent
reply
4 points

The only thing the AIO is missing is #5, and you can probably mount an S3 bucket on the docker host and set the environment variable in the docker-compose.yml accordingly.

I’ve used NC for a long time now in virtually every configuration available from bare metal to snap to NCP, the AIO is by far the easiest thing I’ve ever used to set up and maintain Nextcloud. I wouldn’t be climbing into bed with a proprietary oriented company instead. They will eventually fuck over the users, count on it.

permalink
report
reply
1 point

I’m actually using S3 as Primary Storage Backend. As a result I’ll have to manually backup the database and config files.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 3.7K

    Monthly active users

  • 3.7K

    Posts

  • 79K

    Comments