-
Notifications
You must be signed in to change notification settings - Fork 25
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
feat(Nextcloud): add Nextcloud #193
Conversation
dc12160
to
b00c129
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything worked will trying it the first time :-).
I especially like the generic RedisNameMapper and PostgresReadyCondition.
As we currently never limit cpu, I'm not 100% sure why it would make sense in this case.
From a product point of view the NextCloud installation will benefit from an option of using an s3 bucket as file storage. I Think that we should add this feature as it will also make sense for our own usage.
operator/src/main/kotlin/eu/glasskube/operator/apps/nextcloud/NextcloudSpec.kt
Outdated
Show resolved
Hide resolved
.../src/main/kotlin/eu/glasskube/operator/apps/nextcloud/dependent/NextcloudOfficeDeployment.kt
Outdated
Show resolved
Hide resolved
8ffc227
to
e1c1c25
Compare
Signed-off-by: Philip Miglinci <pmig@glasskube.eu>
Signed-off-by: Philip Miglinci <pmig@glasskube.eu>
Signed-off-by: Philip Miglinci <pmig@glasskube.eu>
Signed-off-by: Philip Miglinci <pmig@glasskube.eu>
Signed-off-by: Philip Miglinci <pmig@glasskube.eu>
No description provided.