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
10 points

Not really what you are asking for, but I found the combination of KaraDAV and Filestash to be a great alternative to Nextcloud, and much more stable for basic use.

As for Owncloud… I am skeptical of the company behind them ever since they split off into them and Nextcloud. Probably better to avoid, regardless of what you think of Nextcloud.

permalink
report
reply
3 points

Filestash looks awesome! I tried the demo on my phone and it was way snappier than Nextcloud or even Google drive lol. I mostly use Nextcloud for documents and for calender and contacts, so I might replace nextcloud soon given how slow it usually is.

permalink
report
parent
reply
8 points

No idea at all, but I am highly interested in your experience. So it would be great if you could came here back to share it with us

permalink
report
reply
6 points

Will do. Still reading docs and blog posts. ❤

permalink
report
parent
reply
3 points

Don’t forget us!

permalink
report
parent
reply
8 points
*

For what it’s worth, I do think OCIS is worthy of switching to if you don’t make use of all of the various apps Nextcloud can do. OCIS can hook into an online office provider, but doesn’t do much more than just the cloud storage as of right now.

That said, the cloud storage and UX performance is night and day between Nextcloud/Owncloud and OCIS. If you’re using a S3 provider as a storage backend, then you only need to ensure backups for the S3 objects and the small metadata volume the OCIS container needs in order to ensure file integrity.

Another thing to note about OCIS: it provides no at-redt encryption module unlike Nextcloud. If that’s important to your use case, either stick with Nextcloud or you will need to figure out how to roll your own.

I know that OCIS does intend to bring more features into the stack eventually (CalDAV, CardDAV, etc.). As it stands currently though, OCIS isn’t a behemoth that Nextcloud/Owncloud are, and the architecture, maintenance is more straightforward overall.

As for open-source: OCIS released and has still remained under Apache 2.0 for its entire lifespan thus far. If you don’t trust Owncloud over the drama that created Nextcloud, then I guess remain wary? Otherwise OCIS looks fine to use.

permalink
report
reply
2 points

I think I should use it for some time along with Nextcloud AIO. The official documentation is very confusing.

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

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