- Is mapeveri/multi-tenancy-bundle compatible with Laravel?
- No. Despite some listings framing it as a Laravel package, mapeveri/multi-tenancy-bundle is a Symfony bundle. It has no Laravel service provider, facade, config file, or package auto-discovery, so it cannot be installed and used in a Laravel application without a port.
- Does mapeveri/multi-tenancy-bundle support Laravel 11 or Laravel 10?
- No. It targets the Symfony 2 era and Laravel 4-era conventions, well before modern Laravel service providers. There are no declared Laravel version constraints, and the package is not maintained, so it should not be considered for any current Laravel release.
- Is mapeveri/multi-tenancy-bundle still maintained?
- No. The README carries an explicit warning that the repository is not maintained anymore. With roughly 11 stars and zero dependents, there is no active community, fork ecosystem, or patch channel.
- What are the best Laravel alternatives for multi-tenancy?
- For Laravel, evaluate maintained packages such as stancl/tenancy or spatie/laravel-multitenancy. Both are actively maintained and designed around Laravel's service provider and middleware lifecycle. Choose based on whether you need shared-schema row scoping, schema-per-tenant, or database-per-tenant isolation.
- How does mapeveri/multi-tenancy-bundle resolve tenants?
- The bundle uses a config-driven tenant resolver that binds tenant context into the Symfony container during the request lifecycle. It can resolve from domain, subdomain, or request context, but the implementation is Symfony-specific and not wired into Laravel's request pipeline.
- Does mapeveri/multi-tenancy-bundle provide automatic query scoping?
- Conceptually yes—it demonstrates tenant-aware scoping—but the enforcement is built for Symfony/Doctrine, not Laravel Eloquent. In Laravel there is no global scope, connection switcher, or middleware integration out of the box, so you would have to rebuild that layer.
- Can I use mapeveri/multi-tenancy-bundle for production tenant isolation?
- No. Multi-tenancy is a security boundary, and this package is unmaintained with no CVE tracking, no upstream escalation path, and unverified test coverage on isolation paths. Putting it on a customer-data boundary creates asymmetric risk of cross-tenant data exposure.
- How do I install mapeveri/multi-tenancy-bundle?
- You can install it with Composer, but installation is only the first step and does not make it Laravel-compatible. In Symfony you would manually register the bundle; in Laravel there is no service provider to register, so installation alone gives you no working integration.
- Does mapeveri/multi-tenancy-bundle handle queued jobs and Laravel Octane?
- That behavior is unverified. The bundle predates modern Laravel concerns like queued job context propagation, scheduled command tenancy, cache and session namespacing, and long-running workers such as Octane. You would need to prove and likely build that propagation yourself.
- Should I fork mapeveri/multi-tenancy-bundle for my Laravel app?
- Forking is possible but not recommended as a shortcut. Replacing Symfony bundle registration with a Laravel service provider, pinning Composer constraints, and rebuilding Eloquent scoping is effectively a rewrite. A thin internal tenancy layer or a maintained Laravel package is usually a better investment.