cluster-template VS ocis

it's become much easier in the last few years. Talos + Flux + Renovate can be built in a day [0], and simplifies storage/backups/patching even for single-node clusters. There's also a great community, with services like kubesearch [1] providing templates for tons of apps

[0] https://github.com/onedr0p/cluster-template

[1] https://kubesearch.dev

I've been self-hosting a lot of things on a home kubernetes cluster lately, though via gitops using flux (apparently this genre is now home-ops?). I was kind of expecting this article to be along those lines, using the fairly popular gitops starting template cluster-template: https://github.com/onedr0p/cluster-template

I set one of these up on a few cheap odroid-h4's, and have quite enjoyed having a fairly automated (though quite complex of course) setup, that has centralized logging, metrics, dashboards, backup, etc. by copying/adapting other people's setups.

Instead of weechat, I went with a nice web based irc client (the lounge) to replace my irccloud subscription. kubesearch makes it easy to find other people's configs to learn from (https://kubesearch.dev/hr/ghcr.io-bjw-s-helm-app-template-th...).

For populating a homelab Kubernetes cluster, onedr0p has a very nice Flux template: https://github.com/onedr0p/cluster-template

k8s is a lot easier for homelabs than it used to be, and imo it's quicker than nix for building a declarative homelab. templates like this one can deploy a cluster in a few hours: https://github.com/onedr0p/cluster-template

here's my home assistant deployment as a single file: https://github.com/pl4nty/homelab/blob/main/kubernetes/clust...

I deliberately nuked my onprem cluster a few weeks ago, and was fully restored within 2 hours (including host OS reinstalls). and most of that was waiting for backup restores over my slow internet connection

example repo: https://github.com/onedr0p/flux-cluster-template

Magical setups like this often get a lot of bad rap, but if you already understand Ansible and know Linux etc, you might find this repo a good start to building out your own cluster using gitops: https://github.com/onedr0p/flux-cluster-template

more of an end-to-end solution than a build-it-yourself, but this was a huge help in my understanding of k8s and the other tech like gitops - https://github.com/onedr0p/flux-cluster-template

I found a way to do this : just copying the data over WebDAV using rclone (https://github.com/owncloud/ocis/blob/b2323752289d31c4844f36ef71a2ba531bd749c2/docs/ocis/guides/migrate-data-rclone.md)

According to the README[1] on their source repository, that is, flatly, untrue.

They say:

> We are very happy that oCIS does not require a Contributor License Agreement (CLA) as it is Apache 2.0 licensed. We hope this will make it easier to contribute code. If you want to get in touch, most of the developers hang out in our rocket chat channel or reach out to the ownCloud central forum.

They also say:

> Some builds of stable ownCloud Infinite Scale releases provided by ownCloud GmbH are subject to an End User License Agreement.

Which seems both reasonable and sensible...

[1](https://github.com/owncloud/ocis/tree/master)

ownCloud recently released version 3 of ownCloud Infinite Scale (OCIS), which is completely rewritten in Go (which means it's fast) and uses micro-services instead of a PHP monolith. It doesn't have any features like mail/calendar/contacts/chat/etc.. yet, just file sync (but that's all I'm looking for).

This feature request (https://github.com/owncloud/ocis/issues/6558) aims to implement mind-mapping functionality in a free Open Source Software similar to Google Drive called ownCloud Inifite Scale (oCIS).