Dify
LLM app development and orchestration platform.
Category AIPlatforms DockerPrivileges Needs Docker accessChinese docs Full Chinese docsStars ~157K
One-click install command
cp .env.example .envndocker compose up -d
Notes
Run from the repo's docker directory, Docker Compose ≥ 2.24.0; put secrets in a restricted env file.
Agent Prompt
Copy the block below and hand it to an AI Agent — replace [bracketed] parts with your own values.
Deploy Dify (LLM app development and orchestration platform) in my environment. Before starting: 1. Run read-only checks first: OS version, CPU architecture, available disk/RAM, port usage, Docker or sudo access — and report the findings. 2. Use the project source https://github.com/langgenius/dify as ground truth; verify the current stable version, prerequisites and compatibility. 3. Present an execution plan, the files/services/firewall rules to be changed, and a complete rollback plan; wait for my confirmation before executing. 4. Download remote scripts locally for review first; pin tag / image digest / commit; don't rely on latest or master. 5. Never put secrets (passwords, API keys, tokens, subscription URLs) in the prompt, shell history or logs — use 600-permission env files, Docker secrets or _FILE variables instead. Verified starting command (don't run blindly — download/expand and review first): cp .env.example .envndocker compose up -d Project-specific notes: - Run from the repo's docker directory, Docker Compose ≥ 2.24.0; put secrets in a restricted env file. - Permission requirement: Needs Docker access. Don't escalate privileges; don't run containers as root unnecessarily. After execution, verify and report back: - Installed version, service status and health check results; - Open ports, listen addresses, firewall changes; - Config files, data volumes, log and backup locations; - Access method (for sensitive credentials, only state where they're stored — never print them); - Restart policy, plus verified uninstall / rollback commands.