Files
paper-doc/deploy/k8s/10-paper-doc-mcp.yaml
T
govin 48f0c12fd2 frontend: let the writer set a figure's size in the editor
Figures come out of a plotting tool at whatever size they were made. On the
paper this was written for, the sixteen of them are 1441, 1857, 2409 and 4169
pixels wide — every one wider than the 1276px column — so with no size they all
printed at the full width, and the near-square ones (1857×1986, 1974×2068) took
1365px of height, a page each. Measured in the browser, all sixteen came out at
exactly 1276px: not one of them was the size its author wanted.

`{width=…}` has been in the syntax all along, so this is the control that was
missing, not the feature. A row that is a figure now carries 宽度 in its header:
25/50/70/100%, or any value typed in — the size a panel wants is what it
measures, not a round number — with 原尺寸 as the empty value. Beside it, what
the picture will measure on the page (`原图 1857×1986 · 显示 893×955`), worked
out against the column actually rendered behind the dialog, which is the number
the writer is deciding with.

Two rules keep it honest. The value goes through `parseImageWidth` — the same
function that parses the attribute when the paper is printed — so what the
control shows is what will be printed, and a value it cannot read is refused
with the forms that work instead of stored as a size that quietly does nothing.
And the attribute is written into the sentence content by `withImageWidth`,
which edits only the first picture: the control is offered for a figure, and a
sentence with words around its picture is not one. Reading the size back out of
the content rather than keeping a copy of it in the draft means there is one
place it can be wrong instead of two.

`check-image.mjs` grows from 15 checks to 24, driving the real control: that
only figure rows offer one, that it shows what each is set to, that typing 30%
converts to 383×239 immediately, that what was typed is what gets stored, that
the paper then prints it at 30% of the column, that clearing it goes back to the
natural 480×300, and that "宽一点" is refused while the sentence keeps its size.

The MCP side of the same rule was wrong and is fixed with it: `image_upload(width=
"60")` wrote `{width=60px}`, and the reader takes a bare number as a share of the
column — `parseImageWidth` only reads pixels when the value says `px`. A model
asking for 60% got a 60-pixel figure. v7 is deployed with the corrected reading,
and smoke_mcp.py checks it.
2026-09-24 11:25:18 +08:00

215 lines
7.3 KiB
YAML

# paper-doc MCP server: ConfigMap, Deployment, Service.
#
# The REST API and the MCP server are the same image with different commands.
# Only the MCP server is deployed here, because that is what a client connects
# to; the API is described in a commented block at the end of this file rather
# than deployed, so that turning it on is a decision rather than a surprise.
#
# The database is TiDB, already running in this cluster as `tidb-tidb.tidb:4000`
# — the in-cluster Service, not the 32738 NodePort the host uses. Both reach the
# same rows; the Service is the one that survives the node's address changing.
---
apiVersion: v1
kind: ConfigMap
metadata:
name: paper-doc-config
namespace: paper-doc
labels:
app.kubernetes.io/name: paper-doc
data:
DB_HOST: tidb-tidb.tidb
DB_PORT: "4000"
DB_NAME: paper_doc
APP_NAME: paper-doc API
DEBUG: "false"
# Object storage for the images a paper embeds (MinIO, in its own namespace).
# The in-cluster Service, not the host's NodePort 30090: same bucket, and the
# address survives the node changing. The credentials live in the Secret —
# without them `image_upload` answers 「图片存储还没有配置好」 and names the
# variables, while every writing tool keeps working.
MINIO_ENDPOINT: http://minio.minio.svc.cluster.local:9000
MINIO_BUCKET: paper-images
MINIO_REGION: us-east-1
# The container's own defaults, restated here because the Deployment is where
# a reader looks for them.
MCP_TRANSPORT: http
MCP_HOST: 0.0.0.0
MCP_PORT: "8931"
MCP_PATH: /mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: paper-doc-mcp
namespace: paper-doc
labels:
app.kubernetes.io/name: paper-doc
app.kubernetes.io/component: mcp
spec:
# One replica. The server is stateless — every tool opens its own database
# session and closes it — so scaling is safe, but a second replica would only
# add connections to TiDB without adding throughput a model can use.
replicas: 1
strategy:
type: RollingUpdate
rollingUpdate:
maxSurge: 1
maxUnavailable: 0
selector:
matchLabels:
app.kubernetes.io/name: paper-doc
app.kubernetes.io/component: mcp
template:
metadata:
labels:
app.kubernetes.io/name: paper-doc
app.kubernetes.io/component: mcp
spec:
imagePullSecrets:
- name: aliyun-acr
securityContext:
runAsNonRoot: true
runAsUser: 10001
fsGroup: 10001
seccompProfile:
type: RuntimeDefault
containers:
- name: mcp
image: registry.cn-hangzhou.aliyuncs.com/mcp_skill/paper-doc-mcp:v7
imagePullPolicy: IfNotPresent
ports:
- name: http
containerPort: 8931
envFrom:
- configMapRef:
name: paper-doc-config
env:
- name: DB_USER
valueFrom:
secretKeyRef:
name: paper-doc-secrets
key: DB_USER
- name: DB_PASSWORD
valueFrom:
secretKeyRef:
name: paper-doc-secrets
key: DB_PASSWORD
# Without it the HTTP transport is unauthenticated. The server warns
# on stderr when it binds a non-loopback address and finds no token,
# which is the only signal a reader gets that this key is missing.
- name: MCP_HTTP_TOKEN
valueFrom:
secretKeyRef:
name: paper-doc-secrets
key: MCP_HTTP_TOKEN
# The object store's credentials. A key scoped to this one bucket is
# enough: the bucket is created on the first upload, so nothing has
# to be provisioned by hand before the first figure goes in.
- name: MINIO_ACCESS_KEY
valueFrom:
secretKeyRef:
name: paper-doc-secrets
key: MINIO_ACCESS_KEY
- name: MINIO_SECRET_KEY
valueFrom:
secretKeyRef:
name: paper-doc-secrets
key: MINIO_SECRET_KEY
# Readiness asks the database; liveness does not. A TiDB blip should
# take the pod out of the Service's endpoints and put it back when the
# blip ends — not restart a process that is working correctly.
readinessProbe:
httpGet:
path: /readyz
port: http
initialDelaySeconds: 5
periodSeconds: 10
timeoutSeconds: 5
failureThreshold: 3
livenessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 10
periodSeconds: 30
timeoutSeconds: 5
failureThreshold: 3
resources:
requests:
cpu: 50m
memory: 128Mi
limits:
cpu: 1000m
memory: 512Mi
securityContext:
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
capabilities:
drop: ["ALL"]
volumeMounts:
- name: tmp
mountPath: /tmp
volumes:
- name: tmp
emptyDir: {}
---
apiVersion: v1
kind: Service
metadata:
name: paper-doc-mcp
namespace: paper-doc
labels:
app.kubernetes.io/name: paper-doc
app.kubernetes.io/component: mcp
spec:
# NodePort, not ClusterIP: the clients that matter here are not in the
# cluster. The Harness, Claude Code and Codex all run on the node or on a
# machine on the LAN, and `http://192.168.1.88:30931/mcp` is the same address
# from both. In-cluster callers use the ClusterIP on port 8931.
type: NodePort
selector:
app.kubernetes.io/name: paper-doc
app.kubernetes.io/component: mcp
ports:
- name: http
port: 8931
targetPort: http
nodePort: 30931
# --- the REST API, if you want it in the cluster too -------------------------
#
# Same image, different command; it needs no MCP_HTTP_TOKEN and answers on 8000.
# The schema has to exist before the API serves it, which is what the init
# container is for:
#
# ---
# apiVersion: apps/v1
# kind: Deployment
# metadata:
# name: paper-doc-api
# namespace: paper-doc
# spec:
# replicas: 1
# selector:
# matchLabels: {app.kubernetes.io/name: paper-doc, app.kubernetes.io/component: api}
# template:
# metadata:
# labels: {app.kubernetes.io/name: paper-doc, app.kubernetes.io/component: api}
# spec:
# imagePullSecrets: [{name: aliyun-acr}]
# initContainers:
# - name: migrate
# image: registry.cn-hangzhou.aliyuncs.com/mcp_skill/paper-doc-mcp:v7
# command: ["alembic", "upgrade", "head"]
# envFrom: [{configMapRef: {name: paper-doc-config}}]
# env: [...] # the same secret keys as above; the MinIO
# # pair is what lets the API serve the figures
# containers:
# - name: api
# image: registry.cn-hangzhou.aliyuncs.com/mcp_skill/paper-doc-mcp:v7
# command: ["uvicorn", "app.main:app", "--host", "0.0.0.0", "--port", "8000"]
# ports: [{name: http, containerPort: 8000}]
# envFrom: [{configMapRef: {name: paper-doc-config}}]
# env: [...]
# readinessProbe: {httpGet: {path: /api/health, port: http}}