0x00. preface
Talking about your blog, when you were in college at the beginning, the source code was naturally put on gh, and then open Pages in the setting to get the external access link of the blog. After all, a static page does not need any computing environment, as long as it is a cloud service that can host web Pages. At the beginning, the page is generated locally in hexo g, and then the public folder Git is pushed to gh. Later, I learned to use Travis CI continuous integration to Run hexo g, so I don't have to Run hexo g locally anymore. I just need to When the article git in md format is pushed to the warehouse, Travis CI will start to Run, but it is free Travis CI after all. The SLA is not particularly high. Sometimes it will encounter that the task is pushed for half a day or in the pending state, which has been queuing and affecting the use experience... Later gh launched Actions and resolutely migrated Travis Ci to Actions, After all, it's a native service. Although I'm not used to it when I first started, I wrote it according to various examples The yml file was quickly completed. Finally, because gh Pages' hosting server is overseas, the speed of domestic access is not ideal. At this time, we see that there are similar code platforms in China and hosting services are also provided, that is, coding Net, to tell you the truth, coding really has a conscience. Static hosting always doesn't need to spend money. At first, the hosting server is in HK, and the access speed in the mainland is really good. Web hosting has been upgraded several times later. In fact, it has been changed into a more friendly and self-defined way, Finally, upgrade to the source code based on Tencent cloud serverless, put it on COS, and have domestic CDN acceleration. Until recently, I saw the announcement that the service will be officially stopped
Due to the adjustment of product strategy, CODING website hosting will officially stop its service on December 30, 2021. We recommend you to use "cloud development Webify", an application hosting platform specially built for Web developers under Tencent cloud
Although we switched to Tencent cloud to develop Webify, we also launched the "Webify personal site support plan" for developers, so we can safely migrate
0x01. use
In that case, let's go straight to the topic and start the migration. First, go to your cloud "Web application hosting" console
Click new application
Import from gh is used here. Select the warehouse where the blog is located and import
The blog is still based on the old saying of hexo. It automatically recognizes that the framework default is hexo, and there is no need to modify the construction related parameters to deploy the application
Confirm creation
Then, if the deployment fails, you can see that it is still the Jenkins scheme of coding
[2021-12-23 21:31:45] Thu Dec 23 2021 13:31:44 GMT+0000 (Coordinated Universal Time) 29.6 CloudBase Framework::info running 'npx hexo generate' [2021-12-23 21:31:46] INFO Add lazy load attribute to all post [2021-12-23 21:31:46] INFO Add fallback lazy load using lazysizes [2021-12-23 21:31:46] INFO Start processing [2021-12-23 21:31:47] Version 9 of Highlight.js has reached EOL and is no longer supported. [2021-12-23 21:31:47] Please upgrade or ask whatever dependency you are using to upgrade. [2021-12-23 21:31:47] https://github.com/highlightjs/highlight.js/issues/2877 [2021-12-23 21:31:48] Thu Dec 23 2021 13:31:48 GMT+0000 (Coordinated Universal Time) 33.1 CloudBase Framework::error (node:168) Warning: Accessing non-existent property 'lineno' of module exports inside circular dependency [2021-12-23 21:31:48] (Use `node --trace-warnings ...` to show where the warning was created) [2021-12-23 21:31:48] (node:168) Warning: Accessing non-existent property 'column' of module exports inside circular dependency [2021-12-23 21:31:48] (node:168) Warning: Accessing non-existent property 'filename' of module exports inside circular dependency [2021-12-23 21:31:48] (node:168) Warning: Accessing non-existent property 'lineno' of module exports inside circular dependency [2021-12-23 21:31:48] (node:168) Warning: Accessing non-existent property 'column' of module exports inside circular dependency [2021-12-23 21:31:48] (node:168) Warning: Accessing non-existent property 'filename' of module exports inside circular dependency [2021-12-23 21:31:48] fatal: not a git repository (or any of the parent directories): .git [2021-12-23 21:31:48] fatal: not a git repository (or any of the parent directories): .git [2021-12-23 21:31:48] fatal: not a git repository (or any of the parent directories): .git [2021-12-23 21:31:48] fatal: not a git repository (or any of the parent directories): .git [2021-12-23 21:31:48] fatal: not a git repository (or any of the parent directories): .git ...... [2021-12-23 21:31:48] fatal: not a git repository (or any of the parent directories): .git [2021-12-23 21:31:48] FATAL Something's wrong. Maybe you can find the solution here: https://hexo.io/docs/troubleshooting.html [2021-12-23 21:31:48] Error: Command failed: git log --follow -1 --format="%ad" -- /root/cloudbase-workspace/source/_posts/she.md [2021-12-23 21:31:48] fatal: not a git repository (or any of the parent directories): .git [2021-12-23 21:31:48] [2021-12-23 21:31:48] at checkExecSyncError (child_process.js:760:11) [2021-12-23 21:31:48] at execSync (child_process.js:833:15) [2021-12-23 21:31:48] at getUpdated (/root/cloudbase-workspace/node_modules/hexo-filter-date-from-git/index.js:37:19) [2021-12-23 21:31:48] at Hexo.<anonymous> (/root/cloudbase-workspace/node_modules/hexo-filter-date-from-git/index.js:17:22) [2021-12-23 21:31:48] at Hexo.tryCatcher (/root/cloudbase-workspace/node_modules/bluebird/js/release/util.js:16:23) [2021-12-23 21:31:48] at Hexo.<anonymous> (/root/cloudbase-workspace/node_modules/bluebird/js/release/method.js:15:34) [2021-12-23 21:31:48] at /root/cloudbase-workspace/node_modules/hexo/lib/extend/filter.js:62:52 [2021-12-23 21:31:48] at tryCatcher (/root/cloudbase-workspace/node_modules/bluebird/js/release/util.js:16:23) [2021-12-23 21:31:48] at Object.gotValue (/root/cloudbase-workspace/node_modules/bluebird/js/release/reduce.js:166:18) [2021-12-23 21:31:48] at Object.gotAccum (/root/cloudbase-workspace/node_modules/bluebird/js/release/reduce.js:155:25) [2021-12-23 21:31:48] at Object.tryCatcher (/root/cloudbase-workspace/node_modules/bluebird/js/release/util.js:16:23) [2021-12-23 21:31:48] at Promise._settlePromiseFromHandler (/root/cloudbase-workspace/node_modules/bluebird/js/release/promise.js:547:31) [2021-12-23 21:31:48] at Promise._settlePromise (/root/cloudbase-workspace/node_modules/bluebird/js/release/promise.js:604:18) [2021-12-23 21:31:48] at Promise._settlePromise0 (/root/cloudbase-workspace/node_modules/bluebird/js/release/promise.js:649:10) [2021-12-23 21:31:48] at Promise._settlePromises (/root/cloudbase-workspace/node_modules/bluebird/js/release/promise.js:729:18) [2021-12-23 21:31:48] at _drainQueueStep (/root/cloudbase-workspace/node_modules/bluebird/js/release/async.js:93:12) [2021-12-23 21:31:48] at _drainQueue (/root/cloudbase-workspace/node_modules/bluebird/js/release/async.js:86:9) [2021-12-23 21:31:48] at Async._drainQueues (/root/cloudbase-workspace/node_modules/bluebird/js/release/async.js:102:5) [2021-12-23 21:31:48] at Immediate.Async.drainQueues [as _onImmediate] (/root/cloudbase-workspace/node_modules/bluebird/js/release/async.js:15:14) [2021-12-23 21:31:48] at processImmediate (internal/timers.js:464:21)
The error is fatal: not a git repository (or any of the parent directories): Git, confirm that the hexo filter date from git plug-in will update the last update timestamp in the article according to the GIT history. It seems that the local is not git's warehouse, so an error is reported
And you can see that there is also a git add operation
[2021-12-23 21:31:06]+ cd cloudbase-workspace-private [2021-12-23 21:31:06]+ git config --global user.email tcb@tencent.com [2021-12-23 21:31:06]+ git config --global user.name tcb [2021-12-23 21:31:06]+ git add . [2021-12-23 21:31:06]+ git commit -a -m init
Then there's nothing in the back Git folder, no wonder the error report is not git's warehouse
[2021-12-23 21:31:14]+ cd /root/cloudbase-workspace// [2021-12-23 21:31:14]+ pwd [2021-12-23 21:31:14]/root/cloudbase-workspace [2021-12-23 21:31:14]+ ls -al [2021-12-23 21:31:14]total 556 [2021-12-23 21:31:14]drwxr-xr-x 6 root root 4096 Dec 23 13:31 . [2021-12-23 21:31:14]drwx------ 1 root root 4096 Dec 23 13:31 .. [2021-12-23 21:31:14]drwxr-xr-x 3 root root 4096 Dec 23 13:31 .github [2021-12-23 21:31:14]-rw-r--r-- 1 root root 90 Dec 23 13:31 .gitignore [2021-12-23 21:31:14]-rw-r--r-- 1 root root 111 Dec 23 13:31 .gitmodules [2021-12-23 21:31:14]-rw-r--r-- 1 root root 572 Dec 23 13:31 Jenkinsfile [2021-12-23 21:31:14]-rw-r--r-- 1 root root 855 Dec 23 13:31 README.md [2021-12-23 21:31:14]-rw-r--r-- 1 root root 2671 Dec 23 13:31 _config.yml [2021-12-23 21:31:14]drwxr-xr-x 2 root root 4096 Dec 23 13:31 api [2021-12-23 21:31:14]-rw-r--r-- 1 root root 403 Dec 23 13:31 deploy.sh [2021-12-23 21:31:14]-rw-r--r-- 1 root root 508200 Dec 23 13:31 package-lock.json [2021-12-23 21:31:14]-rw-r--r-- 1 root root 969 Dec 23 13:31 package.json [2021-12-23 21:31:14]drwxr-xr-x 5 root root 4096 Dec 23 13:31 source [2021-12-23 21:31:14]drwxr-xr-x 3 root root 4096 Dec 23 13:31 themes [2021-12-23 21:31:14]-rw-r--r-- 1 root root 2 Dec 23 13:31 vercel.json
mark here first. It's time to give feedback and update the article after the feedback results come out