-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: adding support for document server inside the helm chart #214
Comments
Would be very nice |
Agreed - this would be really helpful. I'm trying to implement within a fork, but unfortunately I am new to both nextcloud and collabora, so it is proving fairly painful. |
I think if this was to be added, it would make the most sense to add it as a subchart that can be optionally enabled. Looks like Collabora has a helm chart here: And OnlyOffice has a helm chart here: @tvories, @provokateurin what do you think of this feature? |
Yeah let's use what is already out there. Would be great to validate that it works with a new CI test. |
Agree, I have no idea on this at all. I haven't actually used these together at all. So, let's start by splitting this into two issues:
As for this issue, we could close it with the answer of yes, this sounds like a great idea :) We just need to actually do the work in a compartmentalized fashion. |
I'll close this, more specific discussions can happen in the respective issues. |
It would be cool if the helm chart can support the deployment and the configuration of a document server (Collabora or OnlyOffice) without needing to make a separate deployment.
A simple integration could be to deploy the document server in the same pod as the Nextcloud instance to allow communication over localhost, thus the new feature should be easy to integrate with the existing chart.
The text was updated successfully, but these errors were encountered: