Files
govin 1531263bd2 frontend: let a figure be sized by its height as well as its width
A writer with a tall panel does not want to shrink it from the left edge: what
they know is "this one is too tall". The format had a width and nothing else, so
the only way to make a figure shorter was to guess a percentage and check the
page — and the previous commit's answer, "type 638px", asked them to do the
arithmetic themselves.

So `{height=300px}` joins `{width=…}`, in the same attribute block, and the
editor grows a second box beside the first. Both are typeable as well as
pre-set, both write through the reader's own parse function, and the hint beside
them says what the picture will measure on the page.

Three rules, and the point of all three is that a figure cannot be stretched:

* **a width is exact, a height is a cap.** A width has a reference — the column,
  or a length the writer chose — while nothing measures a height against
  anything, and enlarging a picture past its own pixels only makes it soft. In
  the flow of a sentence a height is always a downscale, which comes to the same
  thing as exact.
* **given one, the other follows from the picture's own shape** — `max-height`
  for a height, `width` for a width — so the height is never written by hand.
* **given both, they are a box to fit inside**, not a box to fill. Two numbers
  that need not have the picture's proportions can only mean "no bigger than",
  and the check asserts the drawn rectangle still matches the file's ratio.

Whichever box is left empty keeps the other's setting, so a size can be set in
two steps, and clearing either goes back to the natural size.

`check-image.mjs`: 26 checks to 36. Two of the new ones found real bugs while
being written. The first: with both a width and a height in one `{…}` block,
neither side parsed — the patterns were anchored to the whole block, so a figure
with two numbers silently printed at its natural size. The attribute block is now
split into declarations first. The second was mine: returning "contain" for a
height-only figure left a 1276×2000 box around a small picture, which the caption
then sat under. A height is a cap, and a cap needs no contain.

The MCP tool takes the same two arguments, so a model can write either number,
and a percentage height is refused with the reason it cannot work: a sentence is
flowed text, so there is nothing for it to be a percentage of and the browser
ignores it. v8 is deployed and DSH has verified both numbers round-tripping.
2026-09-24 13:18:52 +08:00
..

部署到 k3s

paper-doc 的 MCP 服务跑在 k3s 里,命名空间 paper-doc,客户端通过 http://192.168.1.88:30931/mcp 连接。

为什么不是 paper_doc:Kubernetes 的命名空间名必须是 RFC 1123 label, 下划线不在允许的字符集里([a-z0-9]([-a-z0-9]*[a-z0-9])?),API Server 会直接拒绝。 所以命名空间用连字符 paper-doc;数据库名和表名仍然是 paper_doc,两者不冲突。

部署了什么

资源 名字 说明
Namespace paper-doc deploy/k8s/00-namespace.yaml
Deployment paper-doc-mcp 1 副本,跑 MCP 服务的 http 传输
Service paper-doc-mcp NodePort 30931 → 容器 8931
ConfigMap paper-doc-config 非敏感环境变量(数据库地址、监听配置、MinIO 端点与桶名)
Secret paper-doc-secrets DB_USER / DB_PASSWORD / MCP_HTTP_TOKEN / MINIO_ACCESS_KEY / MINIO_SECRET_KEY
Secret aliyun-acr 镜像仓库拉取凭证(从 default 复制)

镜像:registry.cn-hangzhou.aliyuncs.com/mcp_skill/paper-doc-mcp:v8 (sha256:fbbc4b1ab91ce80a3045f2990d85357f1cc267a2644639efe522a25cf42c4bc0; kubectl -n paper-doc get pods -o jsonpath='{.items[0].status.containerStatuses[0].imageID}' 对得上,才说明跑的就是 ACR 上那一版。历史:v1 首发布 → v2 重命名表 → v3 参考文献库 → v4 补参考文献 MCP 工具 → v5 换行与参考文献表 → v6 插图与公式对齐 → v7 插图的宽度写法与页面一致 → v8 插图可分别填宽与高。)

数据库:TiDB 已经在这个集群里,Deployment 用集群内的 Service tidb-tidb.tidb:4000,而不是宿主机用的 NodePort 192.168.1.88:32738。 两者是同一份数据;集群内用 Service 的好处是节点地址变了也不用改配置。

对象存储:论文里的插图放在 MinIO(命名空间 minio,同一个集群)。 集群内用它自己的 Service http://minio.minio.svc.cluster.local:9000, 宿主机上开发才用 NodePort http://192.168.1.88:30090;两边是同一个桶 paper-images, 桶会在第一次上传时自动创建。少给凭证不会让服务起不来:image_upload 会回一句 「图片存储还没有配置好(缺少 MINIO_…)」,写作类工具照常可用。

访问地址

从哪里连 地址
宿主机 / 局域网 http://192.168.1.88:30931/mcp
集群内 Pod http://paper-doc-mcp.paper-doc.svc.cluster.local:8931/mcp
健康检查(免鉴权) http://192.168.1.88:30931/healthz、/readyz

除 /healthz 和 /readyz 外,所有请求都要带 Authorization: Bearer <MCP_HTTP_TOKEN>,否则返回 401。 Token 在 Secret 里,取法:

export KUBECONFIG=$HOME/.kube/config
kubectl -n paper-doc get secret paper-doc-secrets \
  -o jsonpath='{.data.MCP_HTTP_TOKEN}' | base64 -d; echo

日常操作

先记住这一句,否则 kubectl 会去读 root-only 的 /etc/rancher/k3s/k3s.yaml 并报 permission denied:

export KUBECONFIG=$HOME/.kube/config
# 状态
kubectl -n paper-doc get deploy,svc,pods
kubectl -n paper-doc logs deploy/paper-doc-mcp --tail=50

# 重新构建并推送镜像(需要一个 tag,见下面「两个坑」)
deploy/build-mcp-image.sh v3

# 发布新版本
kubectl -n paper-doc set image deployment/paper-doc-mcp \
  mcp=registry.cn-hangzhou.aliyuncs.com/mcp_skill/paper-doc-mcp:v3
kubectl -n paper-doc rollout status deployment/paper-doc-mcp

# 回滚
kubectl -n paper-doc rollout undo deployment/paper-doc-mcp

# 改配置 / 换 token
kubectl -n paper-doc edit configmap paper-doc-config
kubectl -n paper-doc create secret generic paper-doc-secrets \
  --from-literal=DB_USER='Govin' \
  --from-literal=DB_PASSWORD='<tidb-password>' \
  --from-literal=MCP_HTTP_TOKEN="$(openssl rand -hex 32)" \
  --dry-run=client -o yaml | kubectl apply -f -
kubectl -n paper-doc rollout restart deployment/paper-doc-mcp

验证部署——不是看 Pod 是不是 Running,而是真的用 MCP 客户端跑一遍:

cd backend
.venv/bin/python scripts/smoke_mcp.py \
  --url http://192.168.1.88:30931/mcp --token "$(cat /tmp/paper-mcp-token)"
# 47 项检查全过 = 集群里这套东西真的能写论文

构建:为什么是 DinD Pod

这台宿主机上没有容器运行时——k3s 用的是 containerd,节点上的 ctr / crictl 都是 k3s 的软链,谁都不能从 Dockerfile 构建。所以构建放在集群里一个临时的 docker-in-docker Pod 里做,源码通过 hostPath 挂进去(/workspace), 这样构建上下文就是当前工作区,未提交的改动也在里面。

deploy/build-mcp-image.sh 把这一整套包好了:起 Pod → 登录 → 构建 → 推送 → 删 Pod (trap 保证失败也会删)。仓库凭证是从集群里已有的 aliyun-acr-secret 读出来的, 所以脚本里没有任何密码,也不会进 shell history。

两个坑(都踩过了,别再踩)

1. 镜像 tag 复用会发布不出新代码。 Deployment 的 imagePullPolicy: IfNotPresent,节点按 tag 缓存镜像。 用同样的 :v1 重新构建推送后,Pod 重启拿到的还是旧镜像—— 现象是新 Pod 起来了、但行为跟没改一样。每次构建换一个 tag(v2、v3…), 或者临时把 imagePullPolicy 改成 Always(代价是每次启动都要连仓库)。

2. 源码权限 0600 会让容器读不到代码。 工作区的文件是 rw-------,COPY 会把权限一起带进镜像, 于是非 root(uid 10001)的容器启动即 can't open file '/app/scripts/mcp_server.py': [Errno 13] Permission denied, 然后 CrashLoopBackOff。Dockerfile 里 RUN chmod -R a+rX /app 解决—— 镜像里的东西只需要可读,不需要任何人可写。

探针:为什么是两个

探针 路径 语义
liveness /healthz 进程还活着吗——不碰数据库,所以数据库抖一下不会变成反复重启
readiness /readyz 现在能服务吗——执行 SELECT 1,TiDB 不通就把 Pod 摘出 Service,通了自动加回来

失败 readiness 只是把 Pod 从负载均衡里摘掉,失败 liveness 会杀掉进程。 数据库短暂不可用只应该是前者,所以这个分工是刻意的。

还没有部署的

  • REST API:同一个镜像,换 command 即可(uvicorn app.main:app --host 0.0.0.0 --port 8000), 再加一个 init 容器跑 alembic upgrade head。配置模板写在 deploy/k8s/10-paper-doc-mcp.yaml 末尾的注释里,解开注释即可。
  • 前端 SPA:需要额外构建(pnpm build)+ nginx 镜像,目前没做。

文件清单

deploy/
├── build-mcp-image.sh          # DinD 构建并推送镜像
├── README.md                   # 本文件
└── k8s/
    ├── 00-namespace.yaml
    ├── 10-paper-doc-mcp.yaml   # ConfigMap + Deployment + Service(含 API 的注释模板)
    └── secret.example.yaml     # Secret 模板,真值不入库