注意,这个才是今晚真正有价值的!
Dify 本地部署
• docker部署的问题
•得等官
方
发版本
•
自
己
无
法改
• 源码部署的问题
• 难度
大
,但可以抄作业👇!
• https://blog.cloud-mes.com/2024/02/21/inst
a
ll-dify-dot-
a
i-
a
t-rocky-linux-9-dot-3-from-
source-code/
13.
https://github.com/langgenius/dify/blob/main/LICENSE
本地部署的License注意事项
Dify is licensedunder the Ap
a
che License 2.0, with the following
a
ddition
a
l conditions:
1. Dify m
a
y be utilized commerci
a
lly, including
a
s
a
b
a
ckend service for other
a
pplic
a
tions or
a
s
a
n
a
pplic
a
tion development pl
a
tform for enterprises. Should the conditions below be met,
a
commerci
a
l license must be obt
a
ined from the producer:
a
. Multi-ten
a
nt service: Unless explicitly
a
uthorized by Dify in writing, you m
a
y not use the Dify source code to oper
a
te
a
multi-ten
a
nt environment.
- Ten
a
nt De
f
inition: Within the context of Dify, one ten
a
nt corresponds to one worksp
a
ce. The worksp
a
ce provides
a
sep
a
r
a
ted
a
re
a
for e
a
ch ten
a
nt's d
a
t
a
a
nd con
f
igur
a
tions.
b. LOGO
a
nd copyright inform
a
tion: In the process of using Dify's frontend, you m
a
y not remove or modify the LOGO or copyright inform
a
tion in the Dify console or
a
pplic
a
tions. This restriction is
in
a
pplic
a
ble to uses of Dify th
a
t do not involve its frontend.
- Frontend De
f
inition: For the purposes of this license, the "frontend" of Dify includes
a
ll components loc
a
ted in the `web/` directory when running Dify from the r
a
w source code, or the "web" im
a
ge
when running Dify with Docker.
Ple
a
se cont
a
ct business@dify.
a
i by em
a
il to inquire
a
bout licensing m
a
tters.
14.
当然我不是律师
我对License的理解
• 不能改Logo
• 不能通过改代码来打开多空间
•【通过
二
次开发Dify社区版实现多worksp
a
ce功能并且通过worksp
a
ce管理应
用
-Dify
二
次开发
系列-哔哩哔哩】 https://b23.tv/MirehgQ (这个视频是错误的)
• 但是可以通过改代码
支
持其他需求,Ap
a
che License
支
持
• https://git.th
a
pe.com.cn/
a
i/dify/-/commits/th
a
pe?ref_type=HEADS
• 天华建筑有限公司严格遵守License