<anonymous> hexo/node_modules/hexo-util/lib/spawn.js:37:17.

Coding warehouse address change causes Hexo G-D deployment failure.

preface

Some time ago I was busy with my work, and I didn’t update my blog for some time. Today I updated my blog deployment and found that the deployment failed suddenly.

At first, according to the error information, I searched the Internet and found all kinds of answers, but they were not very accurate. Some said that the Git version had to be upgraded to the latest Git version. For this reason, I also upgraded the Mac system and the Git version. But discovery doesn’t solve the problem.

Finally, calm down and analyze the error information, suddenly have a direction, and finally locate is the Coding warehouse address change caused by the sudden deployment failure, also verified their guess.

My blog was on GitHub and Coding at the same time. Coding suddenly changed the rules for the warehouse address. I don’t know.

Reason analysis idea

The way to analyze the problem is as follows:

The solution

Go to the Coding warehouse to view the modified warehouse address, and modify the Coding deployment address. The configuration of the Coding deployment address is in the _config.yml file in the root directory of the: hexo folder. As follows:

Save the configuration problem after the modification, rebuild the hexo g-d generation and deploy, and the deployment is successful. Problem solving.

As for the blog source repository, I also store it on Coding (GitHub does not support private repository before). However, you do not need to modify the repository directory when you upload the blog source code. When git push, it will automatically redirect to the repository address modified by Coding.