Add trusted_domains after installation
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
Installed Nextcloud via helm on a baremetal k8s cluster. Created an ingress from another domain to point to Nextcloud service, but it won't let me visit the site because of a trusted_domain error.
Went back into values.yml and added the new domain, ran:
helm upgrade -n nextcloud nextcloud/nextcloud --values values.yml
However, the config.php did not reflect the new list of trusted domains after restart.
Relevent values.yml
trustedDomains:
- nextcloud.mydomain.com
- nextcloud.mydomain2.com
mydomain2.com is the new domain, did not get added to config.php.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with values.yml and trace how trustedDomains is passed through the Helm chart into Nextcloud's config.php during helm upgrade and restart. Compare the rendered configuration with the resulting config.php, using the reported two domains as the test case. Done means the added domain appears in config.php and Nextcloud accepts requests through the new ingress domain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100