In the previous article " A Free/Unlimited Private Cloud", I have already explained in detail how to use this COS, but I use After a period of time, I think it is necessary to open another article to explain the specific consumption method of COS, after all, there are still many functions.

# Picture bed

Someone on Github open sourced a PicGo, the backend can use COS as a picture bed to store files, it is not much better than other picture beds, and the file quality is not good It will be compressed and not mushy. And the file is controllable, because it is on your own cloud.

The specific usage method is here: PicGo.

# Anti-leech

The most important thing about the picture bed is anti-leeching, because COS is a public cloud, anyone who has a link to your file can download the file you saved on COS without restriction.

Enter Storage Bucket List in the left column of the Object Storage Console, click on the bucket you want to set anti-leech, after entering, the File List will be displayed by default, and select Basic Configuration. example:

There is an anti-leech setting on this page, which is turned off by default. example:

Click Edit here, if there is a current status, click it, and the blacklist, whitelist and Referer box will appear. The whitelist means that only the domain name or IP that appears here can link to the resources in this bucket. The blacklist means that it is forbidden to appear in The domain names here link resources in this bucket.

Click Save here to set up the anti-leech chain. (But there is a shortcoming, my Typora can't preview the pictures I put in the picture bed~

# Cold storage

Because COS has 50GB of free space, if it is simply used as a picture bed, it will not be used up. I backed up a part of the almost unused files on Google drive to COS, but I don’t need real-time access to this file at all, and I will download it unless other backup data is lost, so I need to let It stays in the bucket safely and is not downloaded by anyone, including myself.

The specific method is still the same as the anti-leech setting above, the difference is that you need to set a domain name that cannot access the bucket at all, such as gop.com. And if you want to share the file link out. The most important point is that the backup file needs to be encrypted before uploading.

# Static website

There is a "Static Website" option at the bottom of the "Basic Configuration" column. I tried it, and I can publish Hexo in this storage bucket. Those who are interested can check my mirror site: TSTR. It is basically the same as this site, but it should not be updated in the future.

The required operation is: put all the files in the public folder generated by hexo into the bucket, and enable the static website function of the bucket, set the index document to index.html, and enable mandatory https. example:

50 G, I don't think I can use it up anyway, so I just tossed around 😄. (I hope Tencent employees can't see this article~