ocis VS charts

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).

Spinning up workloads in kubernetes is much different than just spinning up a container in docker or even with docker compose. If someone has not already packaged it in a helm chart or some other kubernetes workload you'll have to develop one yourself. There are some nice library charts you can use as a base that should handle just about any random docker image you want to deploy. https://github.com/bjw-s/helm-charts/tree/main/charts/library/common there is also a repo of pre developed charts for common images. https://github.com/k8s-at-home/charts but be aware it was recently deprecated so it won't be receiving any updates.

Take a look at https://github.com/k8s-at-home/charts (recently deprecated but still a fantastic resource) - there are charts for the popular Arrs , tools, etc. You could deploy each chart individually into a namespace, or you could create yourself an "umbrella" chart which pulls in all the necessary charts as dependencies.

Library charts. A very thorough example can be seen here and usages of it here.

Could it be related to this? https://github.com/k8s-at-home/charts/pull/1435/files

I'd submitted a helm chart at https://github.com/k8s-at-home/charts/tree/master/charts/stable/firefly-iii if you want to try out

I know /u/stefantigro means well but the way you are both doing the helm charts is not ideal, helm charts are meant to be shared, not as a means to install apps into your cluster from a local folder. While they can be, it's not a good pattern. Take the helm chart from here for example. This is a published helm chart you can install using the commands in the Readme and you only need to provide the configuration for your instance from the values.yaml file. You can take a look at the values I use for this helm chart here. You can also see I'm using an custom Sonarr image, this image is tailored to running in Kubernetes

There is a working Helm chart for k8s-at-home that should be a good starting point. The biggest hurdle I see is that homebridge can conflict with SCALE's mDNS service as seen in this linked post.

There's an actual helm chart published here.