Extras Laravel Package

Product Decisions This Supports

• Feature direction: Enables runtime/lazy resolution of filesystems by name, useful for multi-tenant storage, per-region buckets, environment-specific disks, or feature-flagged storage backends without hardcoding a concrete filesystem in domain code.
• Roadmap: Treat as a legacy compatibility shim, not a strategic platform dependency. Its last release was 2017 and it has low adoption, so it should not drive new storage architecture.
• Build vs. buy: For a greenfield Laravel product, prefer Laravel’s native Storage/Flysystem disk configuration or a small internal resolver. Consider this package only where an existing Gaufrette stack already depends on the “Resolvable Filesystem” pattern.
• Use cases: Migrating legacy Gaufrette applications, decoupling application code from concrete filesystem implementations, test doubles, tenant-specific filesystem selection, and gradual storage-backend migration.
• Risk decision: Low opportunity score (0.38), unknown repository provenance, and no release since 2017 mean adoption should require explicit ownership, a fork/vendor plan, and a compatibility test matrix.

When to Consider This Package

• You already use Gaufrette and need its resolvable-filesystem behavior rather than introducing a parallel abstraction.
• The scope is small, non-critical, and can be pinned to a known version.
• Your PHP/Laravel versions are verified compatible, or you are prepared to fork and maintain the package.
• You need a thin, testable resolver rather than a full storage platform.

Look elsewhere when:

• You are building a new Laravel application and can use Storage::disk() with Flysystem directly.
• You need active maintenance, security patches, PHP 8+/current Laravel support, or vendor-backed SLAs.
• Storage is business-critical, multi-cloud, or expected to evolve quickly.
• The repository cannot be verified or the dependency would be hard to replace later.

How to Pitch It (Stakeholders)

Executives: This is a low-cost, low-strategic-value utility for legacy Gaufrette environments. It can reduce coupling between application code and storage backends, but it is not a growth lever and carries maintenance risk due to age and low adoption. Approve only as a contained legacy dependency, with a fork/exit plan and no expectation of vendor support.

Engineering: The package offers a resolvable-filesystem abstraction around Gaufrette. Before adopting, compare it with Laravel’s native storage disks and a small custom resolver. If adopted, vendor or fork it, pin the version, add integration tests across supported PHP/Laravel versions, and keep it out of security-critical paths.