OpenCloud

[lstoeferle]

I would like to request a new image to run a self-hosted instance of OpenCloud, an open-source file sharing and collaboration solution. I know the project is still very young and there is already existing support for Nextcloud, but OpenCloud might become a very viable alternative due to the fact that it is developed from the ground up as a cloud-native solution.

For more detailed information about OpenCloud's features, deployment options, and community involvement, you can visit their official website at opencloud.eu.

[RodoMa92]

Yep, Nextcloud is fine but I never liked the slowness associated with it, and it has far too many features in smaller deployments IMO. I'm currently trying OpenCloud and it is league faster than Nextcloud, but the default docker-compose recipes is quite involved (even just for adding Collabora CODE support), so I would like a pre made image if possible.

[thespad]

They already offer their own Docker image, is there something specific that they don't provide that you think a Linuxserver image would be able to?

[RodoMa92]

Mainly less complexity with it, I would like to avoid an additional proxy in the middle for handling communication between opencloud and code, and better docs.

[drizuid]

it looks pretty simple and extensible to me. they document how to do anything a user could want pretty thoroughly too...

[rogervn]

I don't agree the default image instructions are simple. They bundle a whole repository for the docker compose container which includes dependencies optional compose files, dependencies configs and even text configs.

It is not easy to automate that in a declarative way and there's way too many sources of truth for configuration, so I'm giving up on it because of that.

[drizuid]

yah i don't follow what you're saying...
init the container (first time setup)
start the container and login
use whatever envvars you need, use your env file... this is pretty normal stuff
the source for truth for configuration is the official documentation...

regardless, i'm not seeing any interest from the team in recreating the wheel, so it's not something we'll put effort into.

[rogervn]

No worries, the wording might have come out stronger than what I intended.

My point is that I usually automate all my self hosted applications and the default docker compose repo has a mixture of basic default files (like banned passwords and config files not exposed by the docker compose) that are expected to be there to even get to call init, which was surprising to me.

Then it goes into different docker compose yamls that need to be stacked per dependency but the default one is already stacked with several dependencies itself, some of them which have environment variables split between different compose files.

It looked to be fairly complicated and threw me out as I expect that to be simplified in the future because I don't think I'm the only one thrown off by it. I could spend more time and find out all the files that are exposed on the repo that should be on the image or created by init, but chances are they'll create more over time and break my automation, so I just don't and will keep using another option like ocis or nextcloud.