- What is micjohnson/weed-php used for?
- micjohnson/weed-php is a PHP client for Weed-FS, the predecessor to SeaweedFS, a distributed file system for binary and object storage. It is intended as an infrastructure adapter that lets PHP applications talk to the Weed-FS HTTP API for operations such as assigning file IDs, uploading, reading, and deleting files. It is not a general-purpose filesystem abstraction for Laravel.
- Does micjohnson/weed-php work with Laravel?
- It can work inside a Laravel application, but the evaluation notes it probably does not ship a native Laravel Flysystem adapter or service provider. You would likely wrap it behind an application-owned storage interface or build a custom Flysystem adapter. Do not let its classes leak into controllers, jobs, or domain services.
- Is Weed-FS the same as SeaweedFS?
- Weed-FS is the earlier name for what became SeaweedFS, a simple and highly scalable distributed file system. The package targets the legacy Weed-FS HTTP API, while modern SeaweedFS offers an S3-compatible API that is a stronger architectural fit for greenfield Laravel storage. Confirm which protocol version your cluster exposes before committing.
- How do I install micjohnson/weed-php?
- Install it with Composer using the package name micjohnson/weed-php, but first verify that the repository is accessible and that a tagged Composer release exists. The evaluation flags an unknown repository and low adoption, so dependency validation is mandatory. Pin the dependency and audit its transitive HTTP client requirements before adding it to a Laravel project.
- Does micjohnson/weed-php provide a Laravel Flysystem adapter?
- Based on the technical evaluation, the package likely exposes low-level Weed-FS operations rather than a native Laravel Flysystem adapter. To use Laravel's Storage facade, you would need to write a custom Flysystem adapter or a dedicated service provider wrapper. Treat that adapter as application-owned code with its own tests.
- What PHP and Laravel versions does micjohnson/weed-php support?
- The supported PHP and Laravel versions are not confirmed in the available context and must be verified during a dependency audit. The package appears old and low-maintenance, so expect potential incompatibility with modern PHP and Laravel releases. You may need to patch the package or replace its HTTP layer to run on current stacks.
- Is micjohnson/weed-php actively maintained?
- The evaluation rates technical risk as high because the repository is unknown, adoption is low, and Weed-FS itself has been superseded by SeaweedFS. Assume limited upstream support and no security updates unless you verify otherwise. Budget to fork, patch, and maintain the client as internal infrastructure code.
- How does micjohnson/weed-php handle master failover and volume server redirects?
- The available context does not document how the client handles master discovery, volume server redirects, replication, retries, timeouts, or partial writes. These behaviors are key questions that require a non-production spike against a disposable Weed-FS or SeaweedFS cluster. Do not move to production before proving failover and large-file behavior.
- Can I use micjohnson/weed-php in production?
- Only after a repository and dependency audit, a protocol and version spike, and failure testing against a real cluster. The evaluation recommends wrapping or forking the package, adding tests and dependency constraints, and integrating it behind a storage interface. For an existing local or S3 setup, use dual-write, backfill, shadow reads, and a reversible cutover.
- What are alternatives to micjohnson/weed-php for Laravel object storage?
- For modern SeaweedFS, the S3-compatible API is a stronger architectural fit than a dedicated legacy Weed-FS client. Laravel's native S3 filesystem driver can then be used directly, avoiding a custom adapter. If you must stay on Weed-FS, consider forking the client internally or writing a thin HTTP wrapper behind your own storage interface.