Add a dashboard flow to run and understand setup checks
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 54/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- postgresql, typescript
调研方向
Start by reading the existing dashboard patterns and the shared backend check API and result shape referenced in the issue. Trace how checks run in both Cloudflare Workers and Node/Docker deployments, then identify the dashboard entry point and relevant tests. Done means an operator can manually run checks, distinguish all result states, see next steps for failures, and the tests and listed checks pass.
由索引模型根据 Issue 内容生成。
描述
Goal
Give operators a clear dashboard action to run the setup checks from #157 and understand what each result means.
What to build
- Add a clearly named action such as Run setup checks.
- Show each dependency as passed, failed, or unavailable.
- Show a short explanation and a useful next step for failed checks.
- Make it clear that PostgreSQL is checked only after the operator starts the check. Do not add background polling from the dashboard.
- Avoid showing credentials or other secrets in the page.
Implementation guidance
Use the shared API and result shape from the backend checks. Keep the interface consistent with Codra's existing dashboard patterns. The check results must work with both Cloudflare Workers and Node/Docker deployments. If a backend change is needed for the dashboard flow, implement it for both runtimes.
Done when
- An operator can start the checks manually and see results as they complete.
- Passed, failed, and unavailable states are easy to distinguish.
- Failed checks include a useful next step.
- The page does not poll PostgreSQL or expose secrets.
- Tests cover loading, success, failure, unavailable, and error states.
-
npm run typecheck,npm test, andnpm run lintall pass.
- 主要语言
- TypeScript
- 星标
- 125
- 派生
- 23
- 平均合并
- 2 天 13 小时
- 30 天内合并 PR
- 12
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
devarshishimpi/codra 的其他 Issue
-
bug good first issue
难度 2/5 1-3 小时 新手友好度 84/100
devarshishimpi/codra#178 ·
维护者通常 1 天内回复
-
bug good first issue
难度 2/5 1-3 小时 新手友好度 78/100
devarshishimpi/codra#176 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 4/5 3-5 天 新手友好度 48/100
devarshishimpi/codra#186 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 4/5 3-5 天 新手友好度 55/100
devarshishimpi/codra#185 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 4/5 3-5 天 新手友好度 58/100
devarshishimpi/codra#184 ·
维护者通常 1 天内回复
查看 devarshishimpi/codra 的全部 Issue
相似的 Issue
-
难度 1/5 1-3 小时 新手友好度 83/100
gofish-graphics/gofish-graphics#1384 ·
维护者通常 1 天内回复
-
adapter bug
难度 2/5 1-3 小时 新手友好度 83/100
Olanetsoft/agent-lookout#353 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
vicharanashala/vibe#1542 ·
维护者通常 1 天内回复
-
bug chore P2 size:XS
难度 2/5 1-3 小时 新手友好度 77/100
josephfung/curia#2666 ·
维护者通常 1 天内回复
-
area: batch
难度 2/5 1-3 小时 新手友好度 75/100
inabagumi/shinju-date#7294 ·
维护者通常 1 天内回复