Davinci source code deployment-back-end and front-end deployment guide
Davinci source code address:
https://github.com/edp963/davinci
If this URL cannot be entered, it may be walled. You can add relevant domain name resolution to the windows hosts file, such as: 34.120.127.130 artifacts.elastic.co, 52.74.223.119 github.com, 185.199.110.153 edp963.github .io these three hosts domain name resolution, the tool used is the webmaster tool, which can help you choose a near DNS domain name.
Davinci source code back-end deployment process:
There is no problem with the back-end code of this project. It is a mature framework. It uses maven for jar package management. We only need to configure maven to download the jar package by itself to make the program run. However, this place may appear A small bug, as follows: 
The problem encountered may be a problem such as org.elasticsearch.plugin:x-pack-core:7.6.1. The reason for this problem is that an error occurred when Maven went to the remote warehouse to download the jar package, which caused you There is a problem with the jar package of the local maven warehouse, we need to follow the path to find the path of the jar package org.elasticsearch.plugin:x-pack-core:7.6.1, and delete the jar package ending with .lastupdate below it After that, refresh maven and let it re-download. I encountered this problem when deploying Davinci backend. If it still doesn’t work, I can provide the address of a jar package. You can download it and put it into your maven repository. In, the URL is: https://artifacts.elastic.co/maven/org/elasticsearch/client/x-pack-transport/7.6.1/x-pack-transport-7.6.1.jar, I hope it can be useful to you help!
I referred to this blog when I deployed it. The content of this blog is very detailed and it is very good. I hope it will be helpful to you! Link:
https://blog.csdn.net/huzhenv5/article/details/104238590?ops_request_misc=%257B%2522request%255Fid%2522%253A%2522161602907816780269853739%2522%252C%2522scm%2522%253A%252220140713.130102334.pc%255Fblog .%2522%257D&request_id=161602907816780269853739&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2 blog first_rank_v1~rank_blog_v1-2-104238590.pc_v1_rank_blog_v1&utm_term=Davince
Davinci source code front-end deployment process:
For front-end deployment, Davinci uses separation of front-end and back-end, that is to say, I have to install nodejs first and then use npm or cnpm to compile and deploy my front-end code. I refer to this blog for npm deployment, link: https://blog.csdn.net/huzhenv5/article/details/104224241?utm_medium=distribute.pc_relevant.none-task-blog-baidujs_baidulandingword-0&spm=1001.2101.3001.4242
, But my deployment was unsuccessful. The reason is that there may be bugs when using npm deployment. The best way is to use cnpm, such as cnpm install when installing plugins, and cnpm run build when packaging. The front-end deployment I encountered is to use npm to make a mistake, just change to cnpm, and then use cnpm run build to compile the front-end code under the webapp/build file, you copy all the files under webapp/build to the davince of the root directory Under -ui, you can access the page under davince-ui through port 8080.
Reminder:
cnpm的安装：npm install -g cnpm --registry=https://registry.npm.taobao.org
to sum up
The blog is written here, recording the problems I encountered when deploying Davince back-end and front-end. The problems you encountered during deployment may be the same as mine. If it can be helpful to you, this is what I hope to see. If you encounter other problems, I hope you can deal with it calmly, because bugs can always be solved! Let you and I progress together and learn together! The dark horse Jack wishes you all the troubles and obstacles on the road to change bugs!
—Black Horse Jack