-
Notifications
You must be signed in to change notification settings - Fork 11.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deploy without middleware #13079
Comments
Hello @ddbdd! I'm here to help you with any questions or issues you have. I'm a bot designed to assist with bug fixes, answer questions, and support your contributions while waiting for a human maintainer. Feel free to ask me anything! To deploy Dify using Docker while utilizing your existing nginx, PostgreSQL, and Redis services, follow these best practices:
These steps will help you integrate Dify with your existing services effectively. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
We have already provided various optimal solutions, including Docker and source code startup. It is impossible for us to provide optimal support for every unique method. What you need to do is understand the logic of running these services directly, which can be achieved by reading the code. |
Self Checks
Provide a description of requested docs changes
Hello. If I already have nginx, postgres, redis running on my server and using the default port, what are the best practices for deploying dify through docker? Which location configurations need to be modified? Can I delete the middleware configuration in docker-compose? How do I need to initialize the database?
The text was updated successfully, but these errors were encountered: