Another post on the PaaS layer. The next post will probably be Hybrid Cloud.
About a year ago, I deployed my blog on Vercel once. But back then everything felt overwhelming so I stopped there.

So today I’ll continue the grind I left back then.
Start setting up Vercel again
Looking back, I didn’t understand anything and just did random stuff. Now just a glance and in under 5 minutes I can see the issue was the Root Directory choice.

Before, I set it to the /BrokenWorld folder, which made my repo recursive.
Another 10 minutes and the Vercel site was done
Point CNAME to Vercel
While happily preparing to add a CNAME from my domain to Vercel then
An A, AAAA, or CNAME record with that host already exists. For more details, refer to <https://developers.cloudflare.com/dns/manage-dns-records/troubleshooting/records-with-same-name/>.
Welp, I had already pointed an A record to Cloudfly hosting, so doing this too isn’t allowed. So the failover dream went poof
Mission Failed
Also while doing this, I ran into some NodeJs errors in the hosting build package because upgrading to Hexo 8.0.0 made it incompatible with NodeJs 18 => Updating the build file to NodeJs 20 fixed it.

Comments
Join the conversation
Leave a comment
No comments yet
Be the first to share your thoughts!