nextcloud issueshttps://open.greenhost.net/stackspin/nextcloud/-/issues2024-03-28T13:28:57Zhttps://open.greenhost.net/stackspin/nextcloud/-/issues/1113Look into using new docker image hooks2024-03-28T13:28:57ZArie PetersonLook into using new docker image hookshttps://github.com/nextcloud/docker#auto-configuration-via-hook-folders
This might allow us to simplify the chart. See also https://github.com/nextcloud/helm/pull/525https://github.com/nextcloud/docker#auto-configuration-via-hook-folders
This might allow us to simplify the chart. See also https://github.com/nextcloud/helm/pull/525https://open.greenhost.net/stackspin/nextcloud/-/issues/1112setup-apps.sh upgrades pinned apps from app store2024-02-22T11:12:50ZArie Petersonsetup-apps.sh upgrades pinned apps from app storeWe pin most of the nextcloud apps we install to a specific version. However, it seems that the `occ upgrade` that we perform as part of the `setup-apps.sh` script upgrades apps beyond the pinned version, taking the latest compatible vers...We pin most of the nextcloud apps we install to a specific version. However, it seems that the `occ upgrade` that we perform as part of the `setup-apps.sh` script upgrades apps beyond the pinned version, taking the latest compatible version from the nextcloud app store. That's exactly what we don't want.
Probably this is because we temporarily enable the app store during that part of the script. We do that because we install some apps that have a non-standard upstream source, versioning scheme, or lack package artifacts in the github releases. However I believe that by now we have extended the pinning features in our nextcloud chart to the point where we can get all Stackspin-default apps from upstream (github/gitlab) directly and no longer need the app store at all. If that is true, we can forego temporarily enabling the app store, and that should prevent nextcloud from doing any unwanted upgrades.https://open.greenhost.net/stackspin/nextcloud/-/issues/1108setup-apps always installs all apps2023-09-14T08:25:17ZArie Petersonsetup-apps always installs all apps`setup-apps.sh` attempts to check whether a given app version is already installed, but it seems this fails for some reason and it always (re)installs even if the exact same version is already present.`setup-apps.sh` attempts to check whether a given app version is already installed, but it seems this fails for some reason and it always (re)installs even if the exact same version is already present.https://open.greenhost.net/stackspin/nextcloud/-/issues/1107Restart nextcloud on change in setup-apps2024-01-02T13:12:18ZArie PetersonRestart nextcloud on change in setup-appsThe `setup-apps` script is stored in a configmap -- created by helm based on the `apps` helm value. This script is mounted inside the main nextcloud pod. We run the script using `kubectl exec` from a separate Job on helm post-install and...The `setup-apps` script is stored in a configmap -- created by helm based on the `apps` helm value. This script is mounted inside the main nextcloud pod. We run the script using `kubectl exec` from a separate Job on helm post-install and post-upgrade.
This works, *but* if
1. `setup-apps` changes, for example because of a change in the `apps` value, and
2. the `nc-nextcloud` deployment doesn't change
then the deployment still has the old configmap mounted, and so the old version of the script gets run by the post-upgrade script.
Perhaps we can solve this by including a hash of the `apps` value as an annotation on the deployment, but this is tricky because that's created by the upstream nextcloud chart, so we'd have to set it in the `values.yaml` in our chart, so this only works if that particular helm value gets templated by the nextcloud chart :pray:https://open.greenhost.net/stackspin/nextcloud/-/issues/1105Set instance name2023-10-27T14:27:27ZArie PetersonSet instance nameNextcloud has a concept of an "instance name" which is shown to the user in various places, including as the name part of the FROM of email notifications. We should probably set this to a simple but sensible default at installation time,...Nextcloud has a concept of an "instance name" which is shown to the user in various places, including as the name part of the FROM of email notifications. We should probably set this to a simple but sensible default at installation time, perhaps `$domain Nextcloud` or `$domain Stackspin Nextcloud`. It can easily be changed later by the user in the Nextcloud UI so we should make sure that we don't override it again on upgrade.https://open.greenhost.net/stackspin/nextcloud/-/issues/1096Confirming password for admin actions is not possible2023-10-24T10:15:27ZArie PetersonConfirming password for admin actions is not possibleIf your nextcloud session is a bit older (don't know the number), and you try to perform a sensitive operation -- the example I ran into: removing another user from the admin group -- then nextcloud will ask you to "confirm your password...If your nextcloud session is a bit older (don't know the number), and you try to perform a sensitive operation -- the example I ran into: removing another user from the admin group -- then nextcloud will ask you to "confirm your password" before continuing. This is not possible in the SSO setting where we either don't know or don't have a password.
This is a [known issue](https://github.com/zorn-v/nextcloud-social-login/issues/343) for the `sociallogin` app, but the author does not consider it a problem as the app is not aiming at SSO apparently :O.
We could try if another SSO app deals with this problem: #1077 .Futurehttps://open.greenhost.net/stackspin/nextcloud/-/issues/1067Only apply nextcloud config on installation2023-12-20T13:28:58ZArie PetersonOnly apply nextcloud config on installationThe following discussion from !228 should be addressed:
- [ ] @maarten started a [discussion](https://open.greenhost.net/stackspin/nextcloud/-/merge_requests/228#note_49164): (+4 comments)
We currently apply a piece of nextcloud confi...The following discussion from !228 should be addressed:
- [ ] @maarten started a [discussion](https://open.greenhost.net/stackspin/nextcloud/-/merge_requests/228#note_49164): (+4 comments)
We currently apply a piece of nextcloud config on every helm upgrade, which means that the relevant settings will be changed back to these stackspin defaults even if the nextcloud admin has changed them. They are not many settings at the moment (cron type, "same tab" toggle for onlyoffice documents), but it would be confusing and unpleasant if this ever happens.Futurehttps://open.greenhost.net/stackspin/nextcloud/-/issues/1058Migrate all previous Taiko tests to Cypress2023-10-24T10:44:24ZMaarten de WaardMigrate all previous Taiko tests to CypressWhen switching to Cypress we skipped a few simple tests to keep the MR small. To fix this, a `TODO` is present in `cypress/e2e/test-nextcloud.cy.js`
The following discussion from !215 should be addressed:
- [ ] @maarten started a [disc...When switching to Cypress we skipped a few simple tests to keep the MR small. To fix this, a `TODO` is present in `cypress/e2e/test-nextcloud.cy.js`
The following discussion from !215 should be addressed:
- [ ] @maarten started a [discussion](https://open.greenhost.net/stackspin/nextcloud/-/merge_requests/215#note_47515): (+1 comment)
> There's still a TODO hereFuturehttps://open.greenhost.net/stackspin/nextcloud/-/issues/1063Adding full-text-search to Nextcloud2023-03-29T09:35:00ZJanekAdding full-text-search to Nextcloudhttps://github.com/nextcloud/fulltextsearch_elasticsearch/wiki
This enables one to search through text files in nextcloud, when adding OCR even PDFs and co, a far too useful feature not to provide preconfigured out of the box ;)
However...https://github.com/nextcloud/fulltextsearch_elasticsearch/wiki
This enables one to search through text files in nextcloud, when adding OCR even PDFs and co, a far too useful feature not to provide preconfigured out of the box ;)
However, this needs elasticsearch, and I did not find helm charts that incorporate it (like you have with OnlyOffice) - so should we run a separate chart for that?
https://github.com/elastic/helm-charts
There are also Dockerfiles available to combine them: https://github.com/R0Wi/elasticsearch-nextcloud-dockerBackloghttps://open.greenhost.net/stackspin/nextcloud/-/issues/1056Install-helmrelease CI job horribly slow2022-07-07T08:43:11ZVaracInstall-helmrelease CI job horribly slowWhile I was working on #1054 I painfully noticed that the install-helmrelease CI job horribly slow, when resources from previous jobs needed to get removed. See i.e. these both pipeline durations:
![image](/uploads/748835e35241b921dfa25...While I was working on #1054 I painfully noticed that the install-helmrelease CI job horribly slow, when resources from previous jobs needed to get removed. See i.e. these both pipeline durations:
![image](/uploads/748835e35241b921dfa253480f2a0451/image.png)
And i.e. [this install-helmrelease job](https://open.greenhost.net/stackspin/nextcloud/-/jobs/235007) which took `48 minutes 14 seconds` !
Watching the output of latest job I noticed that it hung really long at this step:
```
$ kubectl delete namespace "nc$CI_MERGE_REQUEST_IID" || true
namespace "nc215" deleted
```
I really don't know why.Futurehttps://open.greenhost.net/stackspin/nextcloud/-/issues/1052Health probes fail out of the blue on existing installation2022-12-15T12:40:32ZVaracHealth probes fail out of the blue on existing installationWhile debugging stackspin#1292 I noticed that out of the blue, both Liveness probe and Readiness probe failed for an existing, running NC instance on my varac-test cluster:
```
Warning Unhealthy 25h kubelet ...While debugging stackspin#1292 I noticed that out of the blue, both Liveness probe and Readiness probe failed for an existing, running NC instance on my varac-test cluster:
```
Warning Unhealthy 25h kubelet Startup probe failed: Get "http://10.42.0.242:80/status.php": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Warning Unhealthy 5m5s (x32 over 25h) kubelet Liveness probe failed: Get "http://10.42.0.242:80/status.php": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Warning Unhealthy 2m55s (x41 over 25h) kubelet Readiness probe failed: Get "http://10.42.0.242:80/status.php": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
```
We might want to relac the timeouts a bit.Futurehttps://open.greenhost.net/stackspin/nextcloud/-/issues/1025Publish chart on artifacthub2022-06-30T09:20:49ZVaracPublish chart on artifacthubFuturehttps://open.greenhost.net/stackspin/nextcloud/-/issues/1017Add nextcloud-exporter and scrape it with prometheus2022-04-08T09:16:07ZVaracAdd nextcloud-exporter and scrape it with prometheushttps://github.com/xperimental/nextcloud-exporter
With this we would get metrics like
* nextcloud_up: Indicates if the metrics could be scraped by the exporter...
* nextcloud_free_space_bytes: Free disk space in data directory in byt...https://github.com/xperimental/nextcloud-exporter
With this we would get metrics like
* nextcloud_up: Indicates if the metrics could be scraped by the exporter...
* nextcloud_free_space_bytes: Free disk space in data directory in bytes
* nextcloud_database_size_bytes: Size of database in bytes as reported from engine
* nextcloud_apps_updates_available_total: Number of apps that have available updates
* ...
Not urgent thought.Backloghttps://open.greenhost.net/stackspin/nextcloud/-/issues/1012Renovate: Properly bump appVersion in Chart.yaml on nextcloud of onlyoffice u...2024-02-01T10:33:52ZVaracRenovate: Properly bump appVersion in Chart.yaml on nextcloud of onlyoffice updatessee https://open.greenhost.net/stackspin/stackspin/-/merge_requests/848#note_37540 for the context
or https://open.greenhost.net/stackspin/nextcloud/-/merge_requests/122/diffs for an example MR which updates NC without bumping the appVer...see https://open.greenhost.net/stackspin/stackspin/-/merge_requests/848#note_37540 for the context
or https://open.greenhost.net/stackspin/nextcloud/-/merge_requests/122/diffs for an example MR which updates NC without bumping the appVersion fieldFuturehttps://open.greenhost.net/stackspin/nextcloud/-/issues/1001Auto clean-up package registry2021-12-21T10:02:42ZMaarten de WaardAuto clean-up package registryAfter !84 we probably want to automatically remove helm packages that have been published more than once. This can happen when a pipeline runs several times for the same Chart version. We probably need a solution that would work for all ...After !84 we probably want to automatically remove helm packages that have been published more than once. This can happen when a pipeline runs several times for the same Chart version. We probably need a solution that would work for all helm charts published in several repositories (see stackspin#939)Futurehttps://open.greenhost.net/stackspin/nextcloud/-/issues/995Allow single quotes in OIDC secret2021-11-09T11:27:03ZArie PetersonAllow single quotes in OIDC secretAnd if we can't allow it, Helm should check the value for single quotes and raise an understandable error.
The following discussion from !62 should be addressed:
- [ ] @arie started a [discussion](https://open.greenhost.net/openappstac...And if we can't allow it, Helm should check the value for single quotes and raise an understandable error.
The following discussion from !62 should be addressed:
- [ ] @arie started a [discussion](https://open.greenhost.net/openappstack/nextcloud/-/merge_requests/62#note_31207):
> This breaks if the json happens to contain a single quote, which could easily happen for the `title` field.
>
> [edit] oh not to mention the `clientSecret` one too.Backloghttps://open.greenhost.net/stackspin/nextcloud/-/issues/992Document proper use of overrides2021-11-09T15:02:31ZVaracDocument proper use of overridesWe have https://docs.openappstack.net/en/v0.7/customizing.html#example-customize-nextcloud-to-work-with-staging-certificates
but it's shortcoming in the way that i.e. for nextcloud, simply adding an override is not enough when an applica...We have https://docs.openappstack.net/en/v0.7/customizing.html#example-customize-nextcloud-to-work-with-staging-certificates
but it's shortcoming in the way that i.e. for nextcloud, simply adding an override is not enough when an application is already installed. So we need to document what needs to happen in this case.
I.e.:
* apply override
* reconcile kustomization
* in nextcloud, the configure_apps job is run as an post-upgrade hook so we need to ensure NC is upgraded by the steps aboveFuturehttps://open.greenhost.net/stackspin/nextcloud/-/issues/990Onlyoffice load tests2021-10-26T09:41:07ZVaracOnlyoffice load testsAt some point we should do some load testing for onlyoffice, because we had issues during our weekly meeting when a couple of ppl simultaneously tried to reach the meeting nodes/gantt chart.At some point we should do some load testing for onlyoffice, because we had issues during our weekly meeting when a couple of ppl simultaneously tried to reach the meeting nodes/gantt chart.Futurehttps://open.greenhost.net/stackspin/nextcloud/-/issues/989Dependency Dashboard2024-03-28T23:15:04ZStackspin-renovate BotDependency DashboardThis issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Rate-Limited
These updates are currently rate-limited. Click on a...This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Rate-Limited
These updates are currently rate-limited. Click on a checkbox below to force their creation now.
- [ ] <!-- unlimit-branch=renovate/onlyoffice-onlyoffice-nextcloud-8.x -->Update dependency ONLYOFFICE/onlyoffice-nextcloud to v8.2.4
- [ ] <!-- unlimit-branch=renovate/cypress-terminal-report-5.x-lockfile -->Update dependency cypress-terminal-report to v5.3.12
- [ ] <!-- unlimit-branch=renovate/gruntwork-io-pre-commit-0.x -->Update pre-commit hook gruntwork-io/pre-commit to v0.1.23
- [ ] <!-- unlimit-branch=renovate/rabbitmq-12.x -->Update Helm release rabbitmq to v12.15.0
- [ ] <!-- unlimit-branch=renovate/alpine-k8s-1.x -->Update alpine/k8s Docker tag to v1.29.2
- [ ] <!-- unlimit-branch=renovate/pre-commit-pre-commit-hooks-4.x -->Update pre-commit hook pre-commit/pre-commit-hooks to v4.5.0
- [ ] <!-- unlimit-branch=renovate/rabbitmq-13.x -->Update Helm release rabbitmq to v13
- [ ] <!-- unlimit-branch=renovate/cypress-included-13.x -->Update cypress/included Docker tag to v13
- [ ] <!-- unlimit-branch=renovate/onlyoffice-onlyoffice-nextcloud-9.x -->Update dependency ONLYOFFICE/onlyoffice-nextcloud to v9
- [ ] <!-- unlimit-branch=renovate/cypress-13.x -->Update dependency cypress to v13
- [ ] <!-- unlimit-branch=renovate/cypress-terminal-report-6.x -->Update dependency cypress-terminal-report to v6
- [ ] <!-- unlimit-branch=renovate/onlyoffice-documentserver-8.x -->Update onlyoffice/documentserver Docker tag to v8
- [ ] <!-- create-all-rate-limited-prs -->🔐 **Create all rate-limited MRs at once** 🔐
## Edited/Blocked
These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.
- [ ] <!-- rebase-branch=renovate/nextcloud-4.x -->[Update Helm release nextcloud to v4.6.4](!573)
## Open
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
- [ ] <!-- rebase-branch=renovate/onlyoffice-documentserver-7.x -->[Update onlyoffice/documentserver Docker tag to v7.5.1.1](!568)
## Detected dependencies
<details><summary>gitlabci</summary>
<blockquote>
<details><summary>.gitlab-ci.yml</summary>
- `alpine/k8s 1.28.2`
</details>
</blockquote>
</details>
<details><summary>helm-values</summary>
<blockquote>
<details><summary>values.yaml</summary>
- `onlyoffice/documentserver 7.2.2.56`
- `cypress/included 12.17.4`
</details>
</blockquote>
</details>
<details><summary>helmv3</summary>
<blockquote>
<details><summary>Chart.yaml</summary>
- `nextcloud 4.5.8`
- `rabbitmq 12.2.0`
</details>
</blockquote>
</details>
<details><summary>npm</summary>
<blockquote>
<details><summary>package.json</summary>
- `cypress 12.17.4`
- `cypress-iframe 1.0.1`
- `cypress-terminal-report ^5.0.0`
</details>
</blockquote>
</details>
<details><summary>pre-commit</summary>
<blockquote>
<details><summary>.pre-commit-config.yaml</summary>
- `pre-commit/pre-commit-hooks v4.4.0`
- `gruntwork-io/pre-commit v0.1.22`
</details>
</blockquote>
</details>
<details><summary>regex</summary>
<blockquote>
<details><summary>values.yaml</summary>
- `ONLYOFFICE/onlyoffice-nextcloud v8.2.0`
</details>
</blockquote>
</details>Backloghttps://open.greenhost.net/stackspin/nextcloud/-/issues/982Use helm-docs to create chart documentation2022-04-21T12:20:37ZVaracUse helm-docs to create chart documentationhttps://github.com/norwoodj/helm-docshttps://github.com/norwoodj/helm-docsBacklog