You can execute the following commands to start minikube:
You need to edit values.yaml
and set the persistence type.
For more information, please refer to the Persistent Storage.
Click here to download the
values.yaml
file.
Dify Enterprise is deployed using Helm.
For more information, please refer to the Dify Helm Chart.
You can execute the following commands to enable the Ingress controller on your minikube cluster:
You should use the minikube tunnel
command to expose the services to the host machine.
After Ingress controller is enabled, you can set the domain in your local /etc/hosts
file.
Warning: You have to init Dify Console http://console.dify.local
first before login to Dify Enterprise Dashboard http://enterprise.dify.local
.
http://console.dify.local
.http://enterprise.dify.local
.dashboard@dify.ai
difyai123456
For more information, please refer to the License Activation.
You can execute the following commands to start minikube:
You need to edit values.yaml
and set the persistence type.
For more information, please refer to the Persistent Storage.
Click here to download the
values.yaml
file.
Dify Enterprise is deployed using Helm.
For more information, please refer to the Dify Helm Chart.
You can execute the following commands to enable the Ingress controller on your minikube cluster:
You should use the minikube tunnel
command to expose the services to the host machine.
After Ingress controller is enabled, you can set the domain in your local /etc/hosts
file.
Warning: You have to init Dify Console http://console.dify.local
first before login to Dify Enterprise Dashboard http://enterprise.dify.local
.
http://console.dify.local
.http://enterprise.dify.local
.dashboard@dify.ai
difyai123456
For more information, please refer to the License Activation.