Missing configuration variables in .env file after upgrading to v1.14.2 (Docker Compose)

[yanpx169]

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

Description
I recently upgraded my self-hosted Dify instance (deployed via Docker Compose) to version 1.14.2 and noticed that several previously available environment variables are no longer present in the .env file (specifically the one inside the docker directory).

I would like to ask the maintainers the following questions regarding these changes:

1. Why were these variables removed from the default .env file? Were they deprecated, renamed, or moved to a different configuration method (e.g., database/UI-based settings)?
2. What are the current default values for these variables in v1.14.2 if they are not explicitly set?
3. How can we customize these variables to match our specific requirements (listed below) in the new version? Is it still safe and effective to manually add them back to the docker/.env file and restart the containers, or should we configure them elsewhere?

Missing Variables & Desired Values
The variables I am looking for, along with the values I want to set, are as follows:

WORKFLOW_FILE_UPLOAD_LIMIT=200
UPLOAD_FILE_SIZE_LIMIT=1024
CODE_MAX_STRING_LENGTH=800000
TEMPLATE_TRANSFORM_MAX_LENGTH=800000
WORKFLOW_MAX_EXECUTION_STEPS=1000
WORKFLOW_MAX_EXECUTION_TIME=7200
APP_MAX_EXECUTION_TIME=3600
HTTP_REQUEST_NODE_MAX_TEXT_SIZE=5242880

Environment

• Dify version: 1.14.2
• Deployment method: Docker Compose (Self-hosted)

Any clarification or guidance on how to properly apply these limits in the latest version would be greatly appreciated. Thank you!

---

[dosubot[bot]]

All eight of those environment variables are still active and functional in Dify v1.14.2 — they haven't been removed or deprecated. What changed is their location: the Docker configuration was reorganized from a single docker/.env file into a modular structure under docker/envs/core-services/. The variables now live in docker/envs/core-services/shared.env.example.

Current defaults (from api/configs/feature/__init__.py):

Variable	Default
WORKFLOW_FILE_UPLOAD_LIMIT	10
UPLOAD_FILE_SIZE_LIMIT	15 (MB)
CODE_MAX_STRING_LENGTH	400,000
TEMPLATE_TRANSFORM_MAX_LENGTH	400,000
WORKFLOW_MAX_EXECUTION_STEPS	500
WORKFLOW_MAX_EXECUTION_TIME	1200 (seconds)
APP_MAX_EXECUTION_TIME	1200 (seconds)
HTTP_REQUEST_NODE_MAX_TEXT_SIZE	1,048,576 (bytes)

How to apply your custom values: Copy docker/envs/core-services/shared.env.example to shared.env (in the same directory) and set your desired values there. Alternatively, you can still set them in a root-level docker/.env file or directly as environment variables in your docker-compose.yaml — Dify uses Pydantic's BaseSettings, so any environment variable matching the field name will be picked up regardless of where it's defined [1].

After making changes, restart your containers and they'll take effect immediately. Your desired values are all valid — just note that CODE_MAX_STRING_LENGTH and TEMPLATE_TRANSFORM_MAX_LENGTH defaults were already raised from 80,000 to 400,000 in a previous update [2], so your target of 800,000 is above the new default but should still work fine.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.