- How do I install freyo/flysystem-qcloud-cos-v5 in Laravel?
- Install it with Composer using composer require freyo/flysystem-qcloud-cos-v5, then register the service provider if your Laravel version does not auto-discover it. Add a cos disk entry to config/filesystems.php with your bucket, region, credentials, and any optional CDN domain. The integration is a standard Flysystem disk driver, so application code can keep using the Laravel Storage facade.
- Does freyo/flysystem-qcloud-cos-v5 support Laravel 9, 10, and 11?
- The 2.2.1 release note explicitly adds Laravel 9 support, but the provided evidence does not list exact illuminate/* or laravel/framework constraints for Laravel 10 or 11. Check the package composer.json and run a test install on your target Laravel version before committing. Framework support appears to be added reactively, so verify compatibility rather than assuming it.
- How do I configure a Tencent Cloud COS disk in Laravel config/filesystems.php?
- Add a disk using the cos driver and provide your bucket, region, and credentials, along with an optional CDN domain where needed. The package is designed to slot into Laravel's Storage facade as a custom disk alongside local and s3. Confirm the exact configuration keys in the package README, because the available excerpt does not list every option.
- Does this adapter support temporaryUrl() presigned URLs for Tencent Cloud COS?
- Temporary URL support is not confirmed in the provided release note or evaluation evidence. Flysystem adapters often have gaps around temporaryUrl(), so test Storage::disk('cos')->temporaryUrl() against a real COS bucket before relying on it. If presigned URLs are required, verify this behavior early in your evaluation.
- Does freyo/flysystem-qcloud-cos-v5 support multipart uploads for large files?
- Multipart upload support is not documented in the supplied evidence, even though the underlying Tencent COS PHP SDK may handle large object transfers. Test uploads of representative large files through the Laravel Storage facade before using the adapter for backups or media archives. If the adapter does not expose the behavior you need, direct SDK calls may be required alongside the disk.
- Can I use a custom CDN domain with the Laravel Tencent COS disk?
- The integration notes reference an optional CDN domain in the cos disk configuration, which suggests custom-domain URLs are supported. The exact configuration key and URL-generation behavior are not listed in the provided excerpt. Check the README and test URL output against your CDN setup before production use.
- What PHP and Flysystem versions does freyo/flysystem-qcloud-cos-v5 require?
- The package is identified as a Flysystem v3 adapter for Tencent Cloud COS v5, and it depends on the Tencent COS PHP SDK and Guzzle. Exact PHP and illuminate/* constraints are not included in the provided evidence. Inspect composer.json for the supported PHP and Flysystem matrix, and confirm it resolves on your target stack.
- How does freyo/flysystem-qcloud-cos-v5 compare to overtrue/flysystem-qcloud-cos?
- overtrue/flysystem-qcloud-cos is mentioned as a credible fallback adapter, but the provided evidence does not include a feature-by-feature comparison. Compare both packages on Laravel version constraints, temporaryUrl support, multipart uploads, CDN domains, test coverage, and recent release activity. The portable Storage API makes switching adapters less disruptive if you keep provider-specific calls out of application code.
- Is freyo/flysystem-qcloud-cos-v5 actively maintained and safe for production?
- The evaluation flags maintenance concentration as the primary risk because the 2.2.1 release was a small compatibility change from a first-time contributor, suggesting a limited maintainer pool. Low release cadence can be acceptable for a thin storage adapter, but it becomes a problem if a future Laravel or COS SDK major breaks compatibility. Review release history, issue activity, and the security-reporting path before committing in production.
- How should I test the COS disk and handle credentials securely in Laravel?
- Use an IAM sub-account with least-privilege access to the target bucket, and inject credentials through environment variables rather than committing them to source control. Run integration tests against a dedicated COS test bucket covering uploads, reads, deletes, temporaryUrl, multipart uploads, and custom-domain paths where applicable. The provided evidence does not confirm a CI matrix or live-bucket test coverage, so validate these paths yourself.