When deploying Dify through the local source code, it is impossible to switch to the Milvus vector database.

[harryjudy2240]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.0.0-1.0.1

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

When deploying Dify through the local source code, it is impossible to switch to the Milvus vector database.
The VECTOR_STORE in the ./api/.env file has been set to milvus. However, after restarting, the vector database that is still being connected to is weaviate.

✔️ Expected Behavior

I hope that after setting it to the Milvus vector database, it can be connected to Milvus instead of Weaviate.

❌ Actual Behavior

No response

[ACAne0320]

Did you start the middleware using docker compose -f docker-compose.middleware.yaml --profile weaviate -p dify up -d?
If so, please modify the vector database in docker-compose.middleware.yaml to Milvus.
You can refer to the docker-compose-template.yaml file for the configuration.