There is a problem deploying Dify in a 64 bit Windows 10 environment without Docker. Please help, everyone.

[mzymcm]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

There is a problem deploying Dify in a 64 bit Windows 10 environment without Docker. Please help, everyone.

The first step is to pull, install, and deploy the following:
https://github.com/langgenius/dify.git
https://github.com/langgenius/dify-plugin-daemon.git
Deploy dify.git:
copy .env.example .env
etcd --data-dir=C:\Dify_all\etcd\data
cd C:\Dify_all\weaviate
.\weaviate.exe --scheme=http --host=0.0.0.0 --port=8080
psql -U postgres
CREATE DATABASE dify;
\q
flask db upgrade
poetry run flask run --host 0.0.0.0 --port=5001 --debug
Enter C: \ Dify.all \ dify \ API to execute
poetry run celery -A app.celery worker -P solo --without-gossip --without-mingle -Q dataset,generation,mail,ops_trace --loglevel
Enter the C: \ Dify.all \ dify \ web directory
copy .env.example .env.local
pnpm install
pnpm build
Modify packagejson
Move the 11 lines
"start": "cp -r .next/static .next/standalone/.next/static && cp -r public .next/standalone/public && cross-env PORT=$npm_config_port HOSTNAME=$npm_config_host node .next/standalone/server.js",
Change to:
"start": "cross-env PORT=$npm_config_port HOSTNAME=$npm_config_host node .next/standalone/server.js",
save
cd C:\Dify_all\dify\web
C:\Windows\System32\robocopy.exe ".next\static" ".next\standalone.next\static" /E /MT:8
C:\Windows\System32\robocopy.exe "public" ".next/standalone/public" /E /MT:8
C:\Users\Administrator\AppData\Roaming\npm\pnpm start
Deploy dify-plugin daemon. git:
copy .env.example .env
go build -o plugin-daemon.exe ./cmd/server
cd C:\dify-plugin-daemon
plugin-daemon.exe
The second step is to use it on the client side, and the following error occurs.
The client has no problem from creating a super manager to entering the management page, but there are always errors when adding model suppliers.
After adding the submission, the following error is reported:
{
"code": "invalid_param",
"message": "PluginDaemonBadRequestError: file not found: icon_s_en.svg\nfailed to remap model icon small en_US\nfailed to remap assets\nfailed to save package",
"sta

[dosubot[bot]]

I found 5 similar discussions and issues that might be helpful:

1. Why does deploying Dify without Docker result in fewer plugin daemon services? - This thread discusses the implications of deploying Dify without Docker, which may relate to your deployment issues.

2. PluginDaemonBadRequestError - This thread addresses the same error message you encountered, which could provide insights into resolving your issue.

3. How can I run DIFY locally without Docker? - This discussion explores methods for running Dify locally without Docker, which is directly relevant to your query.

4. After deploying Dify on Windows 10 64 bit system without Docker environment, it was found that there was no plugin daemon service, and the entire Dify system could not work, constantly prompting 500 INTERNAL SERVER ERROR and unable to use. - The suggested solution is to ensure that you have set the necessary environment variables as specified in the web/.env.example and other configuration files, which is crucial for the proper functioning of the Dify system.

5. The installed tool cannot load the icon - This issue was closed by a pull request that fixed missing tool icons, which may relate to the error you are experiencing with the missing icon_s_en.svg file.

[mzymcm]

The robot's response cannot solve this problem. The prerequisite for my problem is a Windows environment without Docker.

[mzymcm]

{
"code": "invalid_param",
"message": "PluginDaemonBadRequestError: file not found: icon_s_en.svg\nfailed to remap model icon small en_US\nfailed to remap assets\nfailed to save package",
"status": 400
}

[mzymcm]

It seems that everyone only deploys in Docker environment. Without Docker, no one can play it. There are no experts, only novices, haha...