purchase a server-> set up the running environment-> start the program-> start listening on a port-> access via IP:PORT

1. determines the architecture
2. purchase resources by schema
3. deployment environment
4. deploy the project to the environment
5. ip Test
6. resolve domain name
7. online testing

if it is pure static deployment (equivalent to running directly with nginx, such as html, css, js), the general idea is to buy an ECS, and find an official image or go to the cloud market to find a matching image (static mainly means that nginx, can find a pagoda panel if it does not want to be afraid of a bunch of command lines), and then assign FTP and whitelist to throw your project up and ip first with ngx,. If there is no problem, then change the DNS parsing, and then test the URL and parsing, it will be fine. Of course, if you have a large number of visitors, you can hang the CDN between the parser and the host.

another naughty idea is to create an OSS, directly and then associate it to CDN (this is described in the best practices of the document, which is equivalent to triggering CDN refresh when a file is updated in OSS), throw the project on OSS, open external access, and finally assign a domain name (to CDN), test, finish the work. But this is only purely static, and if there is a back-end requirement, if it is not a restful call, you may have to add ECS back. (if you call RESTful, you can hang the program on the function calculation, and then hang the API on the API gateway, so that you don't need to use ECS.)