Update dify.yaml

[ebertti]

update for last version of dify docker-compose version, with plugin deamon, fix nginx routes, fix plugin deamon envirioments

Changes

• fix template of dify
• update with last version of dify dify/docker-compose.yaml

Issues

• fix [Bug]: Issue Deploying dify.yaml on Coolify v4.0.0-beta.389 #4964

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic Password	edd8f29	templates/compose/dify.yaml	View secret
-	-	Generic Password	edd8f29	templates/compose/dify.yaml	View secret
-	-	Generic Password	edd8f29	templates/compose/dify.yaml	View secret
-	-	Generic Password	edd8f29	templates/compose/dify.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[andrasbacsai]

update for last version of dify docker-compose version, with plugin deamon, fix nginx routes, fix plugin deamon envirioments

Changes

• fix template of dify
• update with last version of dify dify/docker-compose.yaml

Issues

• fix [Bug]: Issue Deploying dify.yaml on Coolify v4.0.0-beta.389 #4964

Thanks for the PR! I found some issues, could you please check them?

• What is this API key? I hope it's not an actual one ${PLUGIN_DIFY_INNER_API_KEY:-QaHbTe77CtuXmsfyhR7+vRjI/+XbV1AaFy691iy+kGDv2Jvy0/eAh8Y1}
• I saw that you removed some auto-generated passwords and users. Why? the ones with the starting with SERVICE_. For example, for Redis.

[ebertti]

Hi!

Responding to your questions:

What is this API key? I hope it's not an actual one ${PLUGIN_DIFY_INNER_API_KEY:-QaHbTe77CtuXmsfyhR7+vRjI/+XbV1AaFy691iy+kGDv2Jvy0/eAh8Y1}

This is just a default value, but I replace it in a new commit.

Original docker-compose: https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml

I saw that you removed some auto-generated passwords and users. Why? The ones starting with SERVICE_, for example, for Redis.

I removed them because the worker was connecting without a password, only with an empty one. Since this is an internal network, I believe it shouldn't be a big issue.

[peaklabs-dev]

Please do not remove the generated variables, as they create default passwords, users... , so they should be kept if possible.