- How do I install luoyy/ali-oss-storage in a Laravel app?
- Install it with Composer using composer require luoyy/ali-oss-storage, then add an OSS disk entry in config/filesystems.php. Configure the driver name, bucket, endpoint, and access key/secret as documented by the package, preferably through environment variables. Verify the exact driver string and required keys against the package README before deploying.
- Does luoyy/ali-oss-storage support Laravel 10 and Flysystem 3?
- The package is presented as a Laravel filesystem driver built on the Flysystem abstraction, and the technical evaluation frames it as a Laravel 10+ fit. That implies Flysystem 3 and PHP 8.1+, but you should confirm the composer.json constraints for illuminate/support, league/flysystem, and aliyuncs/oss-sdk-php. Loose version constraints on a thin wrapper are worth pinning and testing before adoption.
- How do I configure an Aliyun OSS disk in config/filesystems.php?
- Add a disk entry in config/filesystems.php with the OSS driver, bucket, endpoint, access key, and secret, and optionally a CDN or custom domain. Keep credentials in environment variables rather than committing them to source control. Use the exact key names from the package README, since this is a fork and configuration names may differ from other OSS adapters.
- Can I use Laravel Storage facade methods like put, url, temporaryUrl, and delete with OSS?
- Yes, the package is designed to integrate with the Laravel Storage facade and Flysystem, so existing Storage::disk calls should work without application-level changes if the adapter implements the Flysystem 3 interface Laravel 10 requires. The important caveat is parity: URL generation semantics, visibility and ACL mapping, exists, size, and lastModified behavior can vary between adapters. Build smoke tests against a real bucket for the exact methods your application uses.
- Does the package support CDN domains and signed temporary URLs?
- The package description advertises configurable buckets, endpoints, and CDN domains, so custom domains are part of the intended configuration surface. The technical evaluation specifically flags temporaryUrl signed expiry behavior and custom or CDN domain handling as items to verify in your installed version. Test both public URL generation and temporary URL expiry with your actual bucket and CDN setup.
- Is luoyy/ali-oss-storage actively maintained?
- The available signals are thin: the context reports 14 stars and zero dependents, and the repository URL does not obviously match the Composer package name. It also notes a future-dated last release, which should be treated as a data-quality anomaly rather than proof of active maintenance. Check Packagist, git tag history, issue response times, and commit rights directly before relying on it.
- What are the main risks of using this package in production?
- The biggest risk is maintainership and provenance: this is described as a fork of an original project that stopped updating, and the package-to-repository mapping needs confirmation. The package is also essentially glue over the official Aliyun OSS SDK and Flysystem, so anything the SDK does not expose will not be reachable without forking. With no dependents and little evidence of production hardening, plan your own integration tests and a fallback maintenance path.
- Does it handle large file uploads and multipart uploads?
- The provided context does not confirm whether multipart upload is implemented or what threshold triggers it. Before relying on it for large files, inspect the adapter source and test uploads above your expected multipart threshold. Also test partial failure behavior, retries, and cleanup so failed multipart uploads do not leave orphaned parts in the bucket.
- How should I manage Aliyun OSS credentials securely with this adapter?
- OSS access keys are long-lived by default, so prefer STS temporary credentials or an instance role where your deployment target supports it. The adapter will pass through whatever credentials it is configured with, which means least-privilege policy and rotation are your responsibility. Avoid embedding static keys in code or images, and scope the bucket permissions to only the operations the application needs.
- What alternatives should I consider to luoyy/ali-oss-storage?
- You can use the official aliyuncs/oss-sdk-php directly with a custom Flysystem adapter if you need tighter control over behavior and maintenance. Other community OSS Flysystem adapters may also fit, but compare Laravel version constraints, Flysystem compatibility, temporary URL support, and test coverage. For production, prefer the option with a clear upstream, active release cadence, and a test strategy against a real bucket.