Go to file
Lv, Qi 53d69a00e5 fix(services): make providers observable and robust
- Fix Dockerfile stub builds; compile full sources (no empty binaries)
- Add ca-certificates and curl in runtime images for TLS/healthchecks
- Enable RUST_LOG and RUST_BACKTRACE for all providers
- Add HTTP /health healthchecks in docker-compose for ports 8000-8004
- Standardize Tushare /health to structured HealthStatus JSON
- Enforce strict config validation (FINNHUB_API_KEY, TUSHARE_API_TOKEN)
- Map provider API keys via .env in docker-compose
- Log provider_services at API Gateway startup for diagnostics

Outcome: provider containers no longer exit silently; missing keys fail fast with explicit errors; health and logs are consistent across modules.
2025-11-17 04:40:51 +08:00
.cargo-home/registry/src/github.com-25cdd57fae9f0462/thread_local-1.1.9 refactor(architecture): Align frontend & docs with DB gateway pattern 2025-11-17 01:29:56 +08:00
archive/python chore(cleanup): remove redundant data-distance-service stub tests 2025-11-16 20:52:26 +08:00
config feat: 昨日快照API与前端卡片;注册orgs路由;多项优化 2025-11-05 17:00:32 +08:00
deployment refactor(phase0-1): 容器化与配置服务拆分,并清理根目录 2025-11-08 21:07:38 +08:00
docs refactor(architecture): Align frontend & docs with DB gateway pattern 2025-11-17 01:29:56 +08:00
frontend refactor(architecture): Align frontend & docs with DB gateway pattern 2025-11-17 01:29:56 +08:00
scripts refactor(phase0-1): 容器化与配置服务拆分,并清理根目录 2025-11-08 21:07:38 +08:00
services fix(services): make providers observable and robust 2025-11-17 04:40:51 +08:00
.dockerignore chore(build): unify Dockerfiles and root .dockerignore; fix services after deps upgrade 2025-11-16 23:34:28 +08:00
.gitignore chore: 提交本轮 Rust 架构迁移相关改动 2025-11-16 20:55:46 +08:00
docker-compose.yml fix(services): make providers observable and robust 2025-11-17 04:40:51 +08:00
Tiltfile refactor(phase0-1): 容器化与配置服务拆分,并清理根目录 2025-11-08 21:07:38 +08:00

项目文档中心

欢迎来到基本面选股系统的文档中心。本文档旨在作为项目所有相关文档的入口和导航,帮助团队成员快速找到所需信息。

概览

本文档库遵循特定的结构化命名和分类约定,旨在清晰地分离不同领域的关注点。主要目录结构如下:

  • /1_requirements: 存放所有与产品需求和用户功能相关的文档。
  • /2_architecture: 包含系统高级架构、设计原则和核心规范。
  • /3_project_management: 用于项目跟踪、开发日志和任务管理。
  • /4_archive: 存放已合并或过时的历史文档。
  • /5_data_dictionary: 定义系统中使用的数据模型和字段。

快速导航

以下是项目中几个最核心文档的快速访问链接,直接指向其关键章节。

1. 需求与功能

2. 架构与设计

3. 数据与模型

4. 项目管理