macos - hexo, deploy the blog to github and coding, the code is put, but the content of the blog is not updated when accessed?
PHP中文网2017-05-02 09:31:23
0
9
835
1. Deploy the blog to coding, execute the hexo d command, and you will be prompted with nothing to commit, working directory clean 2. The coding is indeed put, but the content of the blog is not updated when accessing it,
Githubpage will have a delay. It used to be about ten minutes. After the upgrade, it is said that the time is shorter. Based on my experience these past few times, it is basically updated in seconds during the day, but it may take a while at night.
You need to generate public before deploying. You may need to hexo g it. As for not committing, it is because there are no new changes. You can manually change the file content and try again
Dear, did you push to the coding branch called gitcafe-pages? Although coding acquired gitcafe, I remember that the branch name should be coding-pages.
Githubpage will have a delay. It used to be about ten minutes. After the upgrade, it is said that the time is shorter. Based on my experience these past few times, it is basically updated in seconds during the day, but it may take a while at night.
Also pay attention to browser cache.
Recommended: http://idisfkj.github.io/2016/03/04/Hexo-install/
Are you sure you have configured it correctly?
First hexo clean, then hexo g, and finally hexo d
You need to generate public before deploying. You may need to hexo g it. As for not committing, it is because there are no new changes. You can manually change the file content and try again
The prompt "nothing to commit" is usually because the file has not been modified. Make sure you have modified the content before committing.
If the world has not been refreshed after waiting for a long time, you can regenerate it again,
hexo g -d
.Dear, did you push to the coding branch called gitcafe-pages?
Although coding acquired gitcafe, I remember that the branch name should be coding-pages.
I also had this problem just now, and finally found out that the coding branch was not deployed properly. Please check the settings here
Change this branch to the branch where you generated the URL.