Allow setting admin user email via environment variable during initial setup
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- docker, shell
- 领域
- devops, infrastructure
调研方向
首先跟踪处理 NEXTCLOUD_ADMIN_USER 和 NEXTCLOUD_ADMIN_PASSWORD 的容器初始化路径，然后确定提议的管理员电子邮件变量应在哪里应用。使用 SMTP 设置复现一次全新的基于 Docker 的安装，并使用“Basic settings → Test and verify email settings”确认电子邮件已设置，且测试不再因报告的 400 错误而失败。
由索引模型根据 Issue 内容生成。
描述
After a fresh Docker-based install with all SMTP settings supplied via environment variables, the send test via "Basic settings → Test and verify email settings" result in the following error:
AxiosError: Request failed with status code 400
This error message is not helpful and gives no indication of the root cause. It took me several days of debugging - including repeatedly verifying and adjusting the SMTP settings - before I realized that the problem was simply that the admin user had no email address set.
Expected Behavior
A fresh installation should allow specifying an admin email during setup. Without it, the email system silently fails with unclear error messages, despite all SMTP settings appearing correct.
Proposed Solution
Introduce a new environment variable, such as NEXTCLOUD_ADMIN_EMAIL, which can be used during container initialization to automatically assign an email address to the admin user.
environment:
- NEXTCLOUD_ADMIN_USER=admin
- NEXTCLOUD_ADMIN_PASSWORD=secret
- [email protected]
Benefits
- Prevents misleading errors like
AxiosError: Request failed with status code 400when testing email - Reduces time wasted on debugging SMTP configs
- Streamlined, fully automated deployment
- Enables functional email notifications from the start
- Avoids manual post-installation steps
This would align well with the goals of containerization and automation. Thanks for considering!
- 主要语言
- Shell
- 星标
- 7.4k
- 派生
- 1.9k
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nextcloud/docker 的其他 Issue
-
1. To develop bug feature: cron image
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 70/100
-
bug docs
难度 1/5 1 小时以内 新手友好度 72/100
-
0. Needs triage bug
难度 4/5 3-5 天 新手友好度 35/100
-
Imagick architecture mismatch (x86_64 vs aarch64) on official arm64 image causes Apache segfaults未关闭0. Needs triage bug
难度 4/5 3-5 天 新手友好度 50/100
相似的 Issue
-
Install software-properties-common before adding the Suricata PPA可能已有人在做 @himanishpuri 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
Ergane-Foundation/vajra#55 · 2 条评论 ·
维护者通常 2 天内回复
-
[cifuzz] "Minimizing crashes reduces fuzzing time" is logged for every batch run, even with minimize-crashes off可能已有人在做 @martinfrancois 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 90/100
维护者通常 1 天内回复
-
enhancement
难度 1/5 1 小时以内 新手友好度 85/100
alunduil/alunduil-chezmoi#914 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 78/100
obra/superpowers#2505 ·
维护者通常 3 天内回复
-
cao-evolution cao-evolution:compiler-security
难度 1/5 1 小时以内 新手友好度 86/100
githubnext/gh-aw-cao#17586 ·
维护者通常 1 天内回复