docs: refresh localized documentation and Docker flags - #996
Conversation
wyuc
left a comment
There was a problem hiding this comment.
Thanks for refreshing the Chinese documentation. I compared it against the actual registries, configuration paths, and deployment behavior. The built-in provider and model catalogs are accurate, but several gaps should be addressed before approval:
- The Docker
video-exportprofile starts the render service but does not compileNEXT_PUBLIC_ENABLE_VIDEO_EXPORTinto the app, so the export entry remains hidden. The other documentedNEXT_PUBLIC_*flags are also not exposed as Docker build arguments. - Custom OpenAI-compatible providers can currently be added through Settings, but not through arbitrary environment variables or
server-providers.yml. Unknown server-side provider IDs lackproviderTypeand fail during model resolution. - Docker users need explicit guidance for mounting
server-providers.ymland connecting to host-side Ollama, Lemonade, VoxCPM, or ComfyUI services.localhostinside the container points to the OpenMAIC container. - ComfyUI setup, custom TTS/ASR providers, AliDocMind-only audio/video parsing and its supported formats, and
NEXT_PUBLIC_ENABLE_PPTX_IMPORTare still missing from the Chinese docs. The unusedBRAVE_API_KEYexample should also be removed because Brave is keyless.
Please update the other localized documentation at the same time. It is fine to have the agent translate the finalized content consistently across languages.
wyuc
left a comment
There was a problem hiding this comment.
Thanks, most of the previously reported gaps are now addressed. Three items remain before approval:
- The corresponding English, Traditional Chinese, Japanese, Russian, and Arabic pages are still unchanged. Please have the agent propagate the finalized content across all localized documentation.
- The documented
host.docker.internal:8188ComfyUI setup is still rejected by the production SSRF guard becausecomfyui-imageis not server-managed. Please documentALLOW_LOCAL_NETWORKS=truefor this topology, or add a server-managed ComfyUI configuration path. - The documentation says feature flags accept both
trueand1, butNEXT_PUBLIC_ENABLE_PPTX_IMPORTcurrently checks only for the literal valuetrue. Please align the implementation or narrow the documentation.
wyuc
left a comment
There was a problem hiding this comment.
Thanks, the PPTX flag and ComfyUI SSRF guidance are now aligned with the implementation. One localization gap still remains: the latest commit translated only the newly added review-related snippets, rather than the full finalized documentation refresh.
For example, the non-Chinese supported-models pages still list older entries such as GPT-5.4 Mini and Qwen 3.6 while omitting the updated GPT-5.6, Qwen 3.7, Gemini 3.5, and other provider/model entries. The localized configuration pages are also still missing the Lemonade, video generation, default routing, feature flag, and server-option sections, while the localized deployment pages omit PostgreSQL persistence and MP4 export.
Please have an agent translate the complete finalized zh-cn refresh into English, Traditional Chinese, Japanese, Russian, and Arabic, while preserving environment variables, provider IDs, and model IDs exactly.
wyuc
left a comment
There was a problem hiding this comment.
The documentation and localization gaps are now fully addressed. I verified that all five localized guide sets match the finalized Chinese structure, and that environment variables, provider/model IDs, commands, and code blocks remain consistent across languages.
The remaining blocker is the merge conflict with main in tests/config/feature-flags.test.ts. Please resolve it by retaining both the current main tests and the new PPTX feature-flag tests, then let the full PR checks run again.
wyuc
left a comment
There was a problem hiding this comment.
All previously identified documentation, localization, configuration, and deployment gaps are resolved. The merge conflict was handled correctly and the full CI suite passes.
Refresh the localized OpenMAIC documentation and align Docker/client feature-flag behavior with the current implementation.