Repository navigation
docs(deploy): 删除宝塔指南，补 AWS + Caddy 实际部署实录 - #6
Merged
Merged
Conversation
生产最终部署在 AWS EC2 + Caddy（https://sahamdata.top），宝塔那份指南用不上了。 它当初也从未在真实宝塔环境实测过，且是建分支时忘了切回 master、被 PR #3 夹带 合并进来的，留着只会误导。 新增 deploy/aws-caddy.md，记录 2026-07-10 实际跑通的这次部署： 两层反代拓扑、装 Docker、deploy key 拉私有仓库、Caddyfile、备份 cron。 重点是「踩过的坑」一节，全部实际撞到过： - docker compose exec -T 吞 stdin，导致 heredoc / while read 静默截断 - sudo caddy validate 会创建 root:root 的 access.log，让 caddy 启动 permission denied - restart 不重读 .env，改配置必须 --force-recreate - 富化只在入库那一刻发生：先填 key 再抓新闻，顺序反了只能删掉重抓 - 重抓前须清 etag/last_modified，否则条件请求 304 - Caddy 的 reverse_proxy 默认无响应超时（与 nginx 默认 60s 相反） 并归档三个已知问题：IDX 选择器失效但 health 仍报 ok、scheduler 漏掉 HTML 类型源、 中文文案没有确定性合规护栏。 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
为什么删
deploy/baota.md生产最终部署在 AWS EC2 + Caddy（
https://sahamdata.top），宝塔那份指南用不上了。而且它有两个问题：从未在真实宝塔环境实测过（文档开头也如实写了），以及它是我建
fix/分支时忘了先切回master、被 PR #3 夹带合并进来的——流程不干净。留着只会误导下一个接手的人。换成
deploy/aws-caddy.md记录 2026-07-10 实际跑通的这次部署，命令都在真实机器上执行过：两层反代拓扑、装 Docker、用只读 deploy key 拉私有仓库、Caddyfile、备份 cron。
最有价值的是「踩过的坑」一节，全部是这次真撞到的：
docker compose exec -T吞 stdinwhile read循环静默截断，只执行一部分sudo caddy validateroot:root的access.log，caddy 启动 permission denied，报错完全不提日志权限restart不重读.env--force-recreateetagreverse_proxy默认无响应超时，不用调顺带归档三个已知问题
crawl_playwright.py的选择器按旧版结构写死，返回「渲染成功但未抽到匹配的新闻链接」，而health仍标ok——抓取源页面看起来正常，实际零产出。scheduler.py漏掉 HTML 类型源：只查RSS和Playwright，OJK 是HTML，打开定时抓取后它永远不会被自动抓。手动端点sources.py是支持的。rules.py的 34 条禁词全是印尼语/英语，规则层对中文完全失效，只剩 Haiku 语义层兜底。属合规口径，待业务/法务定夺。影响面
纯文档。没有动任何运行中的配置——
docker-compose.prod.yml、两个 Dockerfile、nginx.conf、CI、create_user.py全部保持原样。🤖 Generated with Claude Code