Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Document prod logging to stderr and the optional 5xx error mail (template #162)

已关闭
#233 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
半天
新手友好度
55/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
技术栈
kubernetes, php

调研方向

The facts come from the upstream template change 8bfb0d4 and its prod/monolog.yaml and tests/Unit/Monolog/ProdLogRedactionTest.php, so read those first to confirm the behaviour. The edits go in content/6.deployment/7.troubleshooting.md (logs on stderr, redaction, kubectl logs) and content/6.deployment/4.variables.md (CWA_API_ERROR_MAIL_TO). Done when both pages describe the new behaviour and the variable is listed with the other CWA_API_* settings. Coordinate with docs#232 before merging.

由索引模型根据 Issue 内容生成。

描述

Template change in components-web-app 8bfb0d4's parent (Unreleased; the next release after 2.0.0-alpha.33).

  • Logs: prod writes Google-structured JSON to stderr, not var/log/prod.log. Read them with kubectl logs or the cluster's log explorer (GKE: Cloud Logging, where severity, channel and context are queryable fields). They're redacted: email addresses, JWTs and Authorization values, DSN credentials, bcrypt hashes, and the username and token segments of the email-link URLs. Fit for content/6.deployment/7.troubleshooting.md and the Kubernetes page.
  • Error mail: set the CI variable CWA_API_ERROR_MAIL_TO (with a working MAILER_DSN) to get one email per unique 5xx per hour. The subject is "WEBSITE_NAME API error". Empty sends none. Add it to content/6.deployment/4.variables.md with the other CWA_API_* settings.
  • Browser tests: they now fail a run that sends an error mail. Add this alongside docs#232.
  • For projects: anything new that logs a secret or an email address needs a key or pattern in prod/monolog.yaml, and tests/Unit/Monolog/ProdLogRedactionTest.php covers it.
主要语言
TypeScript
星标
0
派生
0
平均合并
1 小时 20 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

components-web-app/docs 的其他 Issue

查看 components-web-app/docs 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。