Replies: 1 comment 3 replies
-
|
Thanks for the hard work,but I have to say that I still prefer how it was deployed previously. |
Beta Was this translation helpful? Give feedback.
-
|
there's definitely time needed to adjust - but this is a necessary step to separate user-defined configuration from logic. In the future, we'll likely create a script to automate most of the deployment management processes and abstract away the complexities. |
Beta Was this translation helpful? Give feedback.
-
|
Sry for the trouble our work mistake may have caused. We now fully support forward compatibility. If you prefer the old way, you can still use it for deployment; it’s still in the Just wanna explain our intentions for the |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, maybe considering make an app in dify to automatically integrate the env variables into the docker-compose.yaml, so that both the new deployment and and legacy methods are updated at the same time |
Beta Was this translation helpful? Give feedback.
-
New deployment README
In v0.6.12 (#5744), we've rolled out a major structuring to the current docker compose deployment method.
This is being solidified in the past few days as we address issues and quirks encountered by the community: #5769, #5780, #5783, #5735. We're very grateful for your patience with this process. If you are having trouble with the new docker deployment, please try upgrading to the latest version by running
git pull. after that, follow the commands in the updated getting-started guide to deploy your instance. If you still see issues, open a bug report , and we'll get to it as soon as we can.Even though this introduces some initial friction, we trust that the new compose will better serve our users moving forward with the benefit that it brings.
Beta Was this translation helpful? Give feedback.
All reactions