The office is down one person who quit and one who’s off having a baby, so the workload is only going to get heavier.
A couple of days ago I followed the crowd and grabbed a Tencent EdgeOne code, then turned on CDN acceleration for this blog. Today I switched it back. It was pure tinkering.
For a blog on a domain without ICP filing, that kind of CDN acceleration doesn’t really buy you anything—unless the blog never had CDN in the first place. My domain is hosted on Cloudflare and already goes through Cloudflare’s CDN, so what was the point of adding another layer? When a domain has no ICP filing, Cloudflare is a foreign company and Tencent EdgeOne is effectively one too, since without filing you can only use overseas nodes. From where I sit, Cloudflare and EdgeOne made no practical difference.
There was another snag: because the domain is hosted on Cloudflare, EdgeOne’s acceleration needed a CNAME. For the root domain, the CNAME record warning mentioned some “flattening” technique EdgeOne couldn’t deploy. It said the warning could be ignored, but then automatic SSL couldn’t be deployed, which was a real hassle.
Worst of all, the blog had been accessible to me before. After all that fiddling, I couldn’t reach it at all without a VPN—whether through Cloudflare or EdgeOne. Entirely self-inflicted.
I’d thought about trying @大发’s method for deploying EdgeOne Pages directly through code. For one thing, I didn’t know how to do it; for another, without ICP filing it wouldn’t mean much. I lost the mood. Cloudflare it is.