How can I use qiniu's image storage as a third-party server solution for discuz?

Qiniu's image storage was originally designed to facilitate the migration of user data. The official suggestion is that after the data is migrated to qiniu, the newly added images will directly allow users (UGC website) uploading to qiniu. However, I found some problems when using discuz's remote attachment to connect to qiniu, which is inconvenient to use... qiniu's image storage was originally designed to make it easier for users to migrate data.

The official suggestion is that after the data is migrated to qiniu, the newly added images will be directly uploaded to qiniu by the user (UGC website ).

However, I found some problems when I used discuz's remote attachment to connect to qiniu, which is inconvenient to use.

However, the image storage function is very convenient.

If I always use image storage as a solution, it means that the images uploaded by the user are saved locally and automatically changed to the URLs of qiniu after being captured by the image once.

What are the disadvantages of direct remote attachment?

All I can think of is
1. Because you want to fetch data from the source site, the first time you open the image, the speed will be slower (but the poster will load the image after posting it, so there is no difference for other users)

2. Will there be additional fees?

3. higher requirements on server hard disk capacity, which is equivalent to an extra storage cost (although not expensive)

4. What should I do?

Reply content:

Qiniu's image storage was originally designed to make it easier for users to migrate data.

The official suggestion is that after the data is migrated to qiniu, the newly added images will be directly uploaded to qiniu by the user (UGC website ).

However, I found some problems when I used discuz's remote attachment to connect to qiniu, which is inconvenient to use.

However, the image storage function is very convenient.

If I always use image storage as a solution, it means that the images uploaded by the user are saved locally and automatically changed to the URLs of qiniu after being captured by the image once.

What are the disadvantages of direct remote attachment?

All I can think of is
1. Because you want to fetch data from the source site, the first time you open the image, the speed will be slower (but the poster will load the image after posting it, so there is no difference for other users)

2. Will there be additional fees?

3. higher requirements on server hard disk capacity, which is equivalent to an extra storage cost (although not expensive)

4. What should I do?

Pulling resources from the origin site directly through the image storage area will be slow for the first time, and the cost will not change in essence. At most, the storage of the origin site will be more than one, and the traffic will be more than one;

Image Storage is a little troublesome, that is, when the image source site updates resources, qiniu will not take the initiative to return to the image source site to pull resources, qiniu preferentially accesses existing resources in the space. Therefore, if the image source station updates resources, you need to call the prefetch interface or actively delete resources of the same name in the qiniu space, allow qiniu to forcibly pull resources from the source during the next visit.