BorisPolonsky / dify-helm

Deploy langgenious/dify, an LLM based app on kubernetes with helm chart
MIT License
177 stars 46 forks source link

dify-helm-0.14.1 faild deploy dify version >=0.3.8 #11

Closed JeromeLiuLly closed 1 year ago

JeromeLiuLly commented 1 year ago

dify-helm vaild to dify console url. example: https://github.com/langgenius/dify/blob/main/api/config.py

self.CONSOLE_API_URL = get_env('CONSOLE_URL') if get_env('CONSOLE_URL') else get_env('CONSOLE_API_URL')
self.CONSOLE_WEB_URL = get_env('CONSOLE_URL') if get_env('CONSOLE_URL') else get_env('CONSOLE_WEB_URL')

helm value.yaml need to add those key。

JeromeLiuLly commented 1 year ago

success way : helm upgrade -i my-release --set 'externalWeaviate.enabled=true' --set 'externalWeaviate.endpoint=http://weaviate.dify.svc.cluster.local' --set 'api.url.api=https://api.dify.linknext.io' --set 'api.url.console=https://cloud.dify.linknext.io' --set 'api.url.app=https://web.dify.linknext.io' --set 'redis.replica.replicaCount=1' --set 'image.api.tag=0.3.9' --set 'image.web.tag=0.3.9' --set 'weaviate.image.tag=1.18.4' --set 'api.persistence.persistentVolumeClaim.existingClaim=pvc-nfs-dify-api' --set 'proxy.log.persistence.persistentVolumeClaim.existingClaim=pvc-nfs-dify-proxy-log' --set 'postgresql.primary.persistence.storageClass=nfs-client' --set 'postgresql.readReplicas.persistence.storageClass=nfs-client' --set 'weaviate.storage.storageClassName=nfs-client' --set 'redis.master.persistence.existingClaim=pvc-nfs-dify-redis-master' --set 'redis.replica.persistence.existingClaim=pvc-nfs-dify-redis-replica' --set 'web.extraEnv[0].name=EDITION' --set 'web.extraEnv[0].value=SELF_HOSTED' --set 'web.extraEnv[1].name=CONSOLE_URL' --set 'web.extraEnv[1].value=https://web.dify.linknext.io' --set 'web.extraEnv[2].name=APP_URL' --set 'web.extraEnv[2].value=https://web.dify.linknext.io' --set 'api.extraEnv[0].name=CHECK_UPDATE_URL' --set 'api.extraEnv[0].value=https://updates.dify.ai' -n dify .

BorisPolonsky commented 1 year ago

Memo

Difference in docker-compose.yaml between 0.3.1 and 0.3.8

BorisPolonsky commented 1 year ago

@JeromeLiuLly Please try out this patch and see if it's solved.

BorisPolonsky commented 1 year ago

We've completed compatibility support in this release

MIGRATION NOTICE

End users may NOT be able to migrate their helm release from chart version 0.14.* with single helm upgrade command. A helm uninstall <release-name> followed by a helm install <the-very-same-release-name> should do the trick, while introducing minor downtime.