-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to deploy dify-api #7
Comments
helm template dify --set 'externalWeaviate.enabled=true' --set 'externalWeaviate.endpoint=http://weaviate.dify.svc.cluster.local' --set 'api.url.api=https://xy-dify.xingyuxinchuan.com' --set 'api.url.console=https://xy-dify.xingyuxinchuan.com' --set 'api.url.app=https://xy-dify.xingyuxinchuan.com' --set 'redis.replica.replicaCount=1' -n dify . > log.yaml log.yaml
|
helm install dify --set 'externalWeaviate.enabled=true' --set 'externalWeaviate.endpoint=http://weaviate.dify.svc.cluster.local' --set 'api.url.api=https://xy-dify.xingyuxinchuan.com' --set 'api.url.console=https://xy-dify.xingyuxinchuan.com' --set 'api.url.app=https://xy-dify.xingyuxinchuan.com' --set 'redis.replica.replicaCount=1' -n dify . --create-namespace
Thanks for your reply. We have successfully replicated the issue on our side. We are still looking to it. |
Hello there. We have confirmed that this issue could be replicated only if release name were set as
We are still investigating what causes the difference. Feel free to share if you could come up with your fix. @JeromeLiuLly |
We have figured out the cause of the issue.
In this case You may choose a different release name for now as workaround. |
We've already made a patch for this problem. It would be included in the next patch release unless further side effect should prevail. Closing this issue. |
dify-api setup Err
[root@VM-0-10-centos ~]# kubectl logs -f -n dify dify-api-5549c8b5d9-ggtkj
Running migrations
INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO [alembic.runtime.migration] Will assume transactional DDL.
Error: 'tcp' is not a valid port number.
how to config this "tcp"
The text was updated successfully, but these errors were encountered: