if ingress tls is enabled, then adjust the config file to overwriteprotocol https as needed so reverse proxy works
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- helm, kubernetes
- 领域
- cloud, infrastructure
调研方向
该 issue 提到了带 TLS 的 Helm ingress 和 custom.config.php 配置，但没有提供仓库路径或测试。首先定位 chart 的 ingress 和 Nextcloud 配置入口，然后验证启用 ingress TLS 后，reverse-proxy 请求无需手动添加所示配置即可正常工作。
由索引模型根据 Issue 内容生成。
描述
Description of the change
Whatever changes are needed to config file to make a reverse proxy work should happen automatically if an ingress is enabled with tls.
Benefits
Folks deploying via helm chart should not have to know that they need to add a config section to get their reverse-proxy to work. It should be enough that they enabled an ingress with tls.
Possible drawbacks
None
Additional information
I had to add the following config to get the reverse-proxy to work, but every one deploying shouldn't have to dig this up every time, it should just be added automatically if an ingress was enabled with tls.
nextcloud:
# this is required or the reverse-proxy w/ ingress won't work
configs:
custom.config.php: |
<?php
$CONFIG = array (
'overwriteprotocol' => 'https',
'filelocking.enabled' => 'true',
'enable_previews' => true,
);
Since I'm not an expert I don't know if this config file overwrites default settings that I might actually need, or if it just appends these to an existing configuration. By just taking care of things for me, in response to enabling an ingress with tls, things will just work by folks who know the details and just take care of what needs to be taken care of automatically.
- 主要语言
- Go Template
- 星标
- 537
- 派生
- 317
- 平均合并
- 2 天 3 小时
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nextcloud/helm 的其他 Issue
-
No native support for REDIS_USER enviroment var可能已有人在做 @jholmes802 于 9 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 68/100
-
Nextcloud pods run as the namespace's default service account: the chart's account is only created with rbac.enabled, which binds the removed PodSecurityPolicy可能已有人在做 @martin-mat 今天认领。 未关闭
难度 3/5 半天 新手友好度 55/100
-
nextcloud.openmetrics.allowedClients is silently ignored unless nextcloud.configs is set可能已有人在做 @JanWelker 于 25 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 78/100
相似的 Issue
-
type: cleanup
难度 2/5 1-3 小时 新手友好度 78/100
googleapis/google-cloud-swift#1477 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
aws/sagemaker-python-sdk#6495 ·
维护者通常 2 天内回复
-
[DOC] Wrong sg_egress_ports range in the Terraform Databricks Guide for AWS Hub & Spoke with Network Firewall可能已有人在做 @akhil9tiet 今天认领。 未关闭docs
难度 1/5 1 小时以内 新手友好度 72/100
databricks/terraform-provider-databricks#6080 · 1 条评论 ·
维护者通常 3 天内回复
-
aws_opensearch_application is missing IamRoleForDataSourceArn, needed for cross account data sources未关闭bug needs-triage service/opensearch
难度 2/5 半天 新手友好度 70/100
hashicorp/terraform-provider-aws#50510 · 3 条评论 · 5 个 reaction ·
维护者通常 1 天内回复
-
difficulty:easy good first issue status:ready type:bug
难度 2/5 1-3 小时 新手友好度 78/100
incyashraj/krate#45 ·
维护者通常 1 天内回复