Generated Files Without the Silent Overwrite: Why TDK CLI Treats Local Config as Derived Artifacts

说明与用途

TDK CLI 从单个声明性 service.json 生成所有必需的配置文件，通过漂移检测保护手动更改，并提供显式重新生成或忽略选项。

问题

Maintaining consistent local infrastructure files (Dockerfiles, Vite configs, nginx configs, etc.) across many services is error‑prone and tedious, especially when AI writes application code but not the surrounding configs.

结果

TDK CLI automates generation of all local infrastructure files, treats them as derived artifacts, and provides explicit drift handling to protect hand‑edited customizations, ensuring consistency across services without silent overwrites.

工作流

• Write a service.json for each service
• Run tdk up to generate config files and start Tilt/Docker environment
• If a generated file is edited, tdk up detects drift and exits with code 2
• Choose to regenerate with tdk config regenerate or run tdk up --ignore-drift to keep customizations

证据

TDK generates the rest (roughly 17 files for a typical frontend) and treats those outputs as derived artifacts rather than source.

来源

If you edit a generated file by hand, tdk up detects the drift (against a stored snapshot) and stops with exit code 2 instead of silently overwriting.

来源