Resources
Dify moves quickly (nodes, Marketplace plugins, Agent shapes). Prefer docs.dify.ai. The links below are what this tutorial was checked against, plus the sibling courses on Kenhuang Academy.
Official
Chinese docs live on the same site under /zh/ paths. Plugins, tools, and some providers come from the Marketplace—they are not a hard-coded core-repo list.
Hardware and Compose steps follow the self-host page: CPU ≥ 2, RAM ≥ 4 GiB, Mac VM 2 vCPU / 8 GiB, Compose 2.24.0+.
Doc paths worth bookmarking
Related tutorials on this site
Dify is visual; LangChain is code-first; Ollama serves local weights; MCP is how those capabilities show up in an IDE. Real projects often use all four.
Tutorial index
- Dify Tutorial
- Introduction
- Installation
- Quick Start
- Model Providers
- Knowledge Base
- Workflow
- Agent
- Publish & API
- Ollama Integration
- Practical Examples
Community and versions
- Bugs and ideas: GitHub Issues / Discussions (
langgenius/dify) - Self-host upgrades: back up
docker/volumesand.env, then diff the new.env.example. Do not freeze an olddocker-compose.yamlforever - This tutorial follows public Community Edition + Cloud docs. Enterprise screens may differ; trust the docs shipped with your build
Four lines of architecture: Dify orchestrates and publishes; LangChain holds logic you want under unit tests; Ollama serves local weights; MCP is how the same capability shows up in an IDE.
Contribute
This guide lives in Kenhuang Academy. When labels, Compose service names, or API fields change, open an issue or PR and update both docs/zh/dify/ and docs/en/dify/.