Four or five years have passed since I first started blogging. My original intent was to record, think, and organize — a little more for my own benefit, and if it could help others too, so much the better. I went from csdn at the very beginning, to deploying Ghost on Linode, to Pages hosting, and finally to settling on a CDN.

In a team, any change to the development workflow must be paired with the corresponding automation tooling. Without a low enough cost of use, the change is meaningless, because nobody will actually use it. In the previous post we covered how to use a CDN for further frontend/backend separation; this

I have been optimizing a project recently. After mapping out the whole chain, I started improving it step by step and found many points that could be improved. What follows are some thoughts on the development model and the deployment approach. I hope they give you some inspiration. 1. Development Background 1.

1. Download the Tool - qshell qshell is a command-line tool built on the public APIs documented by Qiniu to make it easy for developers to test and use Qiniu API services, written in the Go language. The tool currently bundles convenient commands for Qiniu Storage, CDN, and other methods commonly used in Qiniu services.