dify - 💡(How to fix) Fix [Refactor/Chore] Clean up stale Docker env examples [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Clean up stale Docker environment example entries so the documented variables match the configuration that Dify and Docker Compose actually consume.

The update should:

  • apply MYSQL_MAX_CONNECTIONS in the MySQL Compose command instead of hardcoding 1000
  • rename the VikingDB example variable from VIKINGDB_SCHEMA to the code-supported VIKINGDB_SCHEME
  • remove unused prompt/code generation token limit examples
  • remove the unused ENFORCE_LANGGENIUS_PLUGIN_SIGNATURES plugin signature example

Root Cause

Several Docker example variables are currently misleading because they are misspelled, not consumed, or not wired into the Compose command they describe. This can confuse self-hosted users who copy .env.example or middleware.env.example while configuring deployments.

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactors or chores; if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

Description

Clean up stale Docker environment example entries so the documented variables match the configuration that Dify and Docker Compose actually consume.

The update should:

  • apply MYSQL_MAX_CONNECTIONS in the MySQL Compose command instead of hardcoding 1000
  • rename the VikingDB example variable from VIKINGDB_SCHEMA to the code-supported VIKINGDB_SCHEME
  • remove unused prompt/code generation token limit examples
  • remove the unused ENFORCE_LANGGENIUS_PLUGIN_SIGNATURES plugin signature example

Motivation

Several Docker example variables are currently misleading because they are misspelled, not consumed, or not wired into the Compose command they describe. This can confuse self-hosted users who copy .env.example or middleware.env.example while configuring deployments.

Additional Context

This is a Docker configuration example cleanup only.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING