Skip to content

[docs][conf]: improve model configuration instructions and update .gitignore#38

Closed
TriangleMesh wants to merge 2 commits into
coze-dev:mainfrom
TriangleMesh:docs/improve-model-config-instructions
Closed

[docs][conf]: improve model configuration instructions and update .gitignore#38
TriangleMesh wants to merge 2 commits into
coze-dev:mainfrom
TriangleMesh:docs/improve-model-config-instructions

Conversation

@TriangleMesh
Copy link
Copy Markdown

What type of PR is this?

docs: Documentation only changes

Check the PR title.

  • This PR title match the format: [][]: <description>. For example: [fix][backend] flaky fix
  • The description of this PR title is user-oriented and clear enough for others to understand.
  • Add documentation if the current PR requires user awareness at the usage level.

(Optional) Translate the PR title into Chinese.

[docs][conf]: 改进模型配置说明并更新 .gitignore

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en: This PR improves the model configuration setup process by clarifying the documentation and protecting sensitive configuration files, making it consistent with the model configuration approach used in Coze Studio. The changes include:

  1. Documentation improvements: Updated README.md and README.cn.md to provide clearer instructions for model configuration setup, similar to the "Configure the model" process in Coze Studio
  2. Path clarification: Specified full file paths in copy commands to eliminate confusion about working directory
  3. Template file organization: Added template configuration files for various model providers (OpenAI, Volcengine Ark, Claude, DeepSeek, Gemini, Ollama, Qianfan, etc.), providing a template-based approach similar to Coze Studio's model configuration workflow https://github.com/coze-dev/coze-loop/wiki/5.-Model-configuration
  4. Security enhancement: Updated .gitignore to prevent accidental commits of sensitive model configuration files
  5. User experience alignment: The template-copy-edit workflow now mirrors the intuitive model configuration process that users are familiar with from Coze Studio

These changes make the setup process more user-friendly, reduce the likelihood of configuration errors for new users, and provide a consistent experience across the Coze ecosystem.

zh(optional): 此 PR 通过澄清文档和保护敏感配置文件来改进模型配置设置过程,使其与 Coze Studio 中使用的模型配置方法保持一致。更改包括:

  1. 文档改进:更新 README.md 和 README.cn.md,为模型配置设置提供更清晰的说明,类似于 Coze Studio 中的"配置模型"过程
  2. 路径澄清:在复制命令中指定完整文件路径,消除对工作目录的困惑
  3. 模板文件组织:为各种模型提供商添加模板配置文件(OpenAI、火山方舟、Claude、DeepSeek、Gemini、Ollama、千帆等),提供类似于 Coze Studio 模型配置工作流程的基于模板的方法 https://github.com/coze-dev/coze-loop/wiki/5.-Model-configuration
  4. 安全增强:更新 .gitignore 以防止意外提交敏感的模型配置文件
  5. 用户体验对齐:模板-复制-编辑的工作流程与用户在 Coze Studio 中的模型配置过程类似

这些更改使设置过程更加用户友好,减少新用户出现配置错误的可能性,并在整个 Coze 生态系统中提供一致的体验。

(Optional) Which issue(s) this PR fixes:

N/A - This is a documentation and setup improvement PR that doesn't fix a specific reported issue, but enhances the user experience for model configuration setup by aligning it with Coze Studio's approach.

- Update README.md and README.cn.md to clarify model configuration steps
- Add clear instructions to copy template files from the correct path
- Specify full file paths to avoid confusion about working directory
- Add model_config and model_runtime_config files to .gitignore to prevent
  accidental commits of sensitive configuration data
- Add template configuration files for various model providers

The changes make the setup process clearer for new users by:
1. Showing the exact cp command with full paths
2. Removing ambiguous directory navigation instructions
3. Protecting sensitive config files from being committed
4. Providing template files for different model providers
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Jul 28, 2025

CLA assistant check
All committers have signed the CLA.

@yyyhhl
Copy link
Copy Markdown
Collaborator

yyyhhl commented Jul 29, 2025

Our templates are in this path: https://github.com/coze-dev/coze-loop/tree/main/backend/modules/llm/infra/config/model_repo_example . Have you noticed that? Additionally, is your main requirement to maintain the same user experience as Coze-Studio?

@TriangleMesh
Copy link
Copy Markdown
Author

TriangleMesh commented Jul 29, 2025

Our templates are in this path: https://github.com/coze-dev/coze-loop/tree/main/backend/modules/llm/infra/config/model_repo_example . Have you noticed that? Additionally, is your main requirement to maintain the same user experience as Coze-Studio?

Thanks for pointing that out! I missed it! My main goal is to prevent developers from accidentally uploading the API keys after they modifying their config files. Besides, I also noticed that in the readme of Coze Studio, https://github.com/coze-dev/coze-studio/blob/main/README.md?plain=1, they also used the same method of copying the template config file, so I’m submitting this PR to make sure everything is aligned.

@yyyhhl
Copy link
Copy Markdown
Collaborator

yyyhhl commented Jul 29, 2025

That's a good idea, but it involves some code changes. We will inform you of our decision after we evaluate and discuss it.

@yyyhhl
Copy link
Copy Markdown
Collaborator

yyyhhl commented Jul 31, 2025

We plan to develop product features for model management in August. By then, models can be configured directly on the frontend without needing to use YAML files. Therefore, we've decided not to merge this PR for the time being.

@TriangleMesh
Copy link
Copy Markdown
Author

We plan to develop product features for model management in August. By then, models can be configured directly on the frontend without needing to use YAML files. Therefore, we've decided not to merge this PR for the time being.

Got it, thanks for the clarification! Closing this PR for now. Please feel free to ping me if there’s anything I can help with in the future — happy to contribute further!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants