- Does isklv/smb-bundle work with Laravel or only Symfony2?
- The overview describes it as a Samba client for Symfony2 and a Symfony bundle for SMB/CIFS network shares. No Laravel service provider, facade, or Laravel-focused documentation is mentioned in the supplied material. Treat it as Symfony-first and verify the source before assuming Laravel compatibility. If you need Laravel integration, plan to build a thin adapter yourself.
- How do I install isklv/smb-bundle with Composer?
- Composer install is described as trivial using the package name isklv/smb-bundle. There are no release notes for 0.1.0, so confirm the exact constraint in composer.json before adding it. Pin 0.1.0 exactly during evaluation rather than using a caret range. Run resolution in an isolated branch first to catch dependency conflicts.
- What PHP and Laravel versions does isklv/smb-bundle support?
- The supplied material does not state PHP or illuminate constraints, and the package is described as Symfony2-oriented. Because 0.1.0 has empty release notes, the supported matrix is unverified until you read composer.json and source. Establish the PHP floor and Symfony or Laravel major versions before sequencing integration. If it targets a PHP version above your runtime floor, that is a blocker, not an integration detail.
- Is isklv/smb-bundle safe to use in production at version 0.1.0?
- It is a pre-1.0 initial release with limited adoption and sparse documentation. Under SemVer, 0.x minor bumps may include breaking changes, so a 0.1 range constraint is risky on routine updates. There is no evidence in the supplied material of a stability commitment, security disclosure process, or test coverage. Use it only behind an internal adapter and not on a critical path.
- Does isklv/smb-bundle support Laravel package auto-discovery?
- The supplied material does not confirm a Laravel service provider or auto-discovery entry. The package is described as a Symfony2 bundle, so Laravel discovery is unlikely to be documented. Check composer.json extra.laravel and the provider class during source review. If there is no provider, you must register bindings manually in your application.
- How do I configure SMB/CIFS credentials and shares with isklv/smb-bundle?
- The material does not document configuration keys, validation, or whether credentials are read from env or config files. Because sparse documentation is called out, treat configuration as unknown until source review. Avoid calling env directly outside config files, since config caching will break that pattern. Publish any config into a scratch environment and verify idempotent re-publish before relying on it.
- Does isklv/smb-bundle ship migrations or publishable config?
- The supplied material does not state whether migrations or publishable config exist. The evaluation explicitly lists this as something to confirm: namespaced, re-publishable config and reversible migrations. Test publishing in a scratch environment and verify rollback in a branch database. If migrations exist, do not run them on shared environments until rollback is proven.
- How should I test isklv/smb-bundle in a Laravel application?
- Start with Composer resolution in an isolated branch, then boot the provider in a bare Laravel skeleton before trying your real app. Build a smoke integration behind a thin internal adapter and cover it with a test. Run a CI matrix across your supported Laravel and PHP combinations, including config cache enabled. The supplied material shows no evidence of Testbench, PHPStan or Larastan, or a CI matrix in the package itself.
- Who maintains isklv/smb-bundle and how often is it released?
- The supplied material does not name a maintainer, release cadence, or bus factor. It is described as early-stage with limited adoption and empty 0.1.0 release notes. Before adopting, check the repository history, issue activity, and whether a CHANGELOG or upgrade guide exists. Treat an undocumented 0.x package as higher maintenance risk than merely unpolished code.
- What are alternatives to isklv/smb-bundle for SMB access in Laravel?
- The material does not list alternatives, so compare against actively maintained SMB/CIFS clients and Laravel filesystem adapters that fit your PHP matrix. Evaluate whether you need browsing, file operations, or both, and whether a Symfony bundle is acceptable in your stack. If Laravel-native integration matters, prefer a package with a documented service provider and config. Otherwise wrap isklv/smb-bundle behind your own interface to limit switching cost.