[Aotuman] Auto Sync Tencent Cloud Object Storage COS

Design philosophy: This plugin is green and pollution-free. It does not modify the original system’s database image paths, preventing issues if cloud storage fails, network connectivity is lost, or if you no longer want cloud storage. You can deactivate the plugin at any time. With one-click synchronization, your website images and attachments are automatically synced to Tencent Cloud Object Storage (COS), separating images/attachments from website code and diverting traffic for faster website loading speeds.

Feature Overview

• Supports manual and automatic synchronization of images and attachments to Tencent Cloud Object Storage COS (Automatically sync images and attachments to Tencent Cloud Object Storage COS)

• Supports custom regions, e.g., Beijing ap-beijing, Shanghai ap-shanghai, Chengdu ap-chengdu, Hong Kong (China) ap-hongkong, Singapore ap-singapore, Mumbai ap-mumbai, etc.

• Supports custom bucket names

• Supports one-click synchronization of both new and old website images and attachments from the admin panel

• Supports automatic synchronization of uploaded images and attachments to the cloud; real-time sync to Tencent Cloud Storage upon upload, no manual intervention needed+

• Supports switching back to your own website domain for access at any time, preventing issues if Tencent Cloud fails, network problems occur, or if you simply wish to stop using cloud storage. You can switch back anytime.

• Supports access domains

• Supports custom CDN acceleration domains

• Supports debugging functionality for easy error checking

• Compatible with One-Click WeChat Article Grabber, automatically syncing captured images to Qiniu Cloud

• Supports changing the Media Library path to the CDN acceleration domain. Note: Once enabled, the image paths in the admin Media Library will be changed to the custom access domain or CDN acceleration domain specified above. This means the domain path for images/attachments inserted into posts becomes fixed and irreversible, and frontend traffic can no longer switch back to local. Please be aware!