Weave Code
Filesystem Laravel Package
sfcod/filesystem
Sfcod Filesystem is a Laravel package that simplifies working with files and directories through convenient helpers for uploads, storage, copying, moving, and deletion, while integrating cleanly with Laravel's Storage and filesystem abstractions.
sfcod/filesystem is a lightweight filesystem toolkit for Laravel and PHP applications that simplifies common file and directory operations. It provides a clean, expressive API for managing storage disks, reading and writing files, handling uploads, and organizing paths—reducing boilerplate while staying compatible with Laravel’s filesystem conventions.
- Unified disk API for local and remote storage drivers
- Simple file operations for read, write, copy, move, and delete
- Directory helpers for listing, creating, and cleaning paths
- Laravel-friendly integration with configuration and service providers
- Framework-agnostic core usable in plain PHP projects
Frequently asked questions about Filesystem
- What is sfcod/filesystem and what does it do?
- Sfcod/filesystem is a lightweight Laravel and PHP filesystem package that wraps common file and directory operations in convenient helpers. It focuses on managing paths, uploads, storage, and disk interactions so file handling code stays clean and easy to integrate into your application. It acts as a thin convenience layer rather than a full replacement for Laravel's own filesystem components.
- How do I install sfcod/filesystem with Composer?
- Install it with composer require sfcod/filesystem from your Laravel project root. Because it follows standard Laravel package conventions, package discovery should register the service provider automatically. If your application disables discovery, check the repository README for the provider and facade class names so you can register them manually.
- Does sfcod/filesystem work with Laravel's Storage facade and existing disks?
- The package is described as handling disk interactions, so it sits on top of Laravel's filesystem layer rather than replacing it. That means it should work with the disks you already define in config/filesystems.php. Check the README for the exact helper names before refactoring existing Storage calls.
- Which Laravel and PHP versions does sfcod/filesystem support?
- The repository's composer.json is the authoritative source for supported PHP and Laravel versions, so check the require and require-dev sections. Any CI matrix in the GitHub Actions workflows will also show which versions are actually tested. If your project runs an older Laravel release, confirm compatibility there before adding the dependency.
- How do I configure sfcod/filesystem after installing it?
- Configuration details live in the package README on GitHub. Most Laravel packages of this kind ship a publishable config file via php artisan vendor:publish, and the repository will list the exact provider tag if one exists. If you do not need custom behaviour, the defaults plus your existing filesystems config are usually enough.
- Can sfcod/filesystem help with file uploads in Laravel?
- It provides helpers around uploads and storage, which can cut down boilerplate for naming, moving, and storing uploaded files. Validation remains a framework concern, so keep using rules such as file, mimes, and max in your form requests. The usual pattern is to validate first, then pass the validated UploadedFile instance to the package helper.
- How do I test code that uses sfcod/filesystem?
- Use Laravel's Storage::fake() to swap a real disk for an in-memory one during tests, then assert with methods like Storage::disk()->assertExists(). Since the package builds on Laravel's disk layer, faking the disk covers most of its behaviour. For pure path helpers, simple unit tests against the returned strings are usually sufficient.
- Is sfcod/filesystem safe and performant enough for production?
- It is a thin helper layer, so the overhead compared with the underlying disk operations is minimal. For large files, streaming and chunked transfers matter far more than the wrapper, so confirm what the README says about streaming if that is your use case. As with any dependency, review the source and pin a version before shipping.
- What are the alternatives to sfcod/filesystem?
- Laravel's built-in Storage facade and the underlying Flysystem already cover most filesystem needs, and packages like spatie/laravel-medialibrary handle richer media workflows. Choose sfcod/filesystem when you want lightweight path and upload helpers without pulling in a large dependency. If you only need put, get, and delete, the framework alone is sufficient.
- Is sfcod/filesystem actively maintained and how do I report bugs?
- Check the GitHub repository for recent commits, tagged releases, and open issues to gauge how actively it is maintained. Stars, version tags, and CI status are quick signals of overall health. If you hit a bug, open an issue on the repository or submit a pull request with a failing test.
Weaver
How can I help you explore Laravel packages today?