feedback to refine and enhance the deployment process

[JOduMonT]

Self Checks

• 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.

Content

I like your new improved README in docker; it offer more guidance and clarity.

1. If it was mine I would also recommend and stress the fact tha; if these variables are not change, they are by default exposed by the .env.example

• SECRET_KEY=
• DB_PASSWORD=
• REDIS_PASSWORD=
• any vector DB API password such as
  • WEAVIATE_API_KEY=
  • QDRANT_API_KEY=
  • ...

2. I personally simplified my docker-compose ecosystem by using extends.

Sadly with DiFy; I had to rethink everything as the docker-compose.yaml and .env are heavily.

So instead of of integrating DiFy in my old docker-compose.yml master; I had to move all my extends into ./dify/docker/docker-compose.yaml; which work well at the end.

the main issue was how relative path are declared in your docker-compose such as
.env and ./volumes

I beleive it would wonderful to simplify your docker-compose.yaml with extends and so be more flexible to intergrate DiFy into already existant docker ecosystem.