- How do I install and configure aliyuncs/aliyun-oss-php-sdk-laravel?
- Install it with Composer, publish the package config, and register the service provider and facade alias if your Laravel version does not auto-discover them. Put your AccessKey, endpoint, bucket, and SDK options in the published config, preferably sourced from environment variables. The package only wires the official OSS SDK into Laravel; it does not create buckets or manage cloud credentials for you.
- Does this package work with Laravel 9, 10, or 11?
- No, not natively. Its last release was in 2017 during the Laravel 5.4/5.5 and PHP 5.6/7.0 era, and Composer constraints likely pin illuminate/support to 5.x plus old Guzzle versions. Installing on Laravel 9+ would probably require ignored platform requirements, a fork, or both.
- Does it provide a Laravel Storage disk driver for Aliyun OSS?
- No. It binds the raw AliCloud OSS PHP SDK client into the container and gives you a facade and config; it does not implement a Flysystem driver for Storage::disk('oss'). If you need Laravel Storage semantics, use a maintained Flysystem OSS adapter registered as a custom disk or build your own driver.
- How do I upload a file using the OSS facade in Laravel?
- Resolve the facade to get the raw OSSClient, then call the SDK's putObject method with your bucket, object key, and content or file stream. Options such as ACL, headers, and multipart behavior follow the official aliyun-oss-php-sdk API. There is no Laravel Storage::put abstraction unless you add your own driver.
- How do I generate a signed URL with aliyuncs/aliyun-oss-php-sdk-laravel?
- Call the underlying OSSClient signUrl method with the bucket, object key, and expiry seconds. Because the facade exposes the bundled SDK client, signed URL behavior and TTL semantics match that SDK version. If you need temporaryUrl-style Laravel semantics, wrap it in your own storage service.
- Is this package maintained and safe for production use?
- Treat it as high risk for new production work. It is effectively unmaintained, has no releases since 2017, zero dependents, and no security patch cadence, and it does not guarantee PHP 8.x compatibility. Adopting it means either accepting stale dependencies or forking and owning maintenance.
- Which PHP versions does this Aliyun OSS Laravel wrapper support?
- The wrapper targets the PHP 5.6/7.0 era. PHP 8.1 and 8.2 are not guaranteed and may hit deprecations or dynamic property issues in the old SDK. Validate Composer resolution and runtime behavior in a spike before committing.
- Can I dependency-inject the OSS client instead of using the facade?
- Yes. The service provider binds the OSS client into Laravel's service container, so you can type-hint the client in constructors or resolve it from the container. The facade is just another way to reach the same binding; dependency injection is usually cleaner for testing and service classes.
- How should I test an Aliyun OSS integration built with this package?
- Because it returns a raw OSSClient, you do not get Laravel's Storage fake. Use a dedicated non-production bucket, prove credential loading, put/get/delete, listing, and a signed URL in a timeboxed spike, and assert bucket and key conventions. For parity, wrap calls behind an internal interface and test against the same contract you will use for a Flysystem driver or direct SDK adapter.
- What is a better alternative for Aliyun OSS in modern Laravel?
- Use the official aliyuncs/oss-sdk-php directly or with a maintained Flysystem adapter registered as a custom disk through Storage::extend. That preserves Laravel's Storage contract and isolates OSS specifics behind a driver, instead of depending on this abandoned wrapper. Keep an internal ObjectStorage interface so you can migrate operations like putObject, signUrl, and doesObjectExist predictably.