Weave Code
Multi Tenancy Bundle Laravel Package
syonix/multi-tenancy-bundle
Syonix MultiTenancyBundle is a Symfony bundle for adding multi-tenant support to your application. It provides tenant-aware configuration and isolation so you can serve multiple tenants from a single codebase.
A multi tenancy bundle for Symfony 2 apps
Frequently asked questions about Multi Tenancy Bundle
- What is syonix/multi-tenancy-bundle used for?
- It is a Symfony bundle for adding multi-tenant support to Symfony 2 applications, providing tenant-aware configuration and isolation so one codebase can serve multiple tenants. It is not a Laravel package. Evaluate it only if you are maintaining a legacy Symfony 2 app that needs tenant support.
- Can I install syonix/multi-tenancy-bundle in Laravel?
- No. It is a Symfony 2 bundle, not a Laravel package, and Composer installation alone will not integrate it with Laravel's service container, routing, or Eloquent. Laravel apps should use Laravel-specific tenancy packages instead. Attempting to use this bundle in Laravel would require substantial custom integration and is not recommended.
- How do I install syonix/multi-tenancy-bundle with Composer?
- Install it via Composer using the package name syonix/multi-tenancy-bundle, then register the bundle in your Symfony 2 app's kernel and configure it according to the bundle documentation. Because the public README details may be sparse, check the repository source and bundle class for required configuration. This is a legacy Symfony 2 workflow, not Laravel package discovery.
- Which Symfony versions does syonix/multi-tenancy-bundle support?
- The package is described as a Symfony 2 bundle, so it targets Symfony 2 applications. It is not advertised as compatible with Symfony 3, 4, 5, 6, or later. Verify the composer.json constraints before assuming compatibility with any modern Symfony version.
- Does syonix/multi-tenancy-bundle support Laravel 10 or Laravel 11?
- No. The package is built for Symfony 2 and does not provide Laravel service providers, facades, migrations, or Eloquent tenancy hooks. Laravel 10 and 11 require a Laravel-native tenancy solution. Do not expect this bundle to work with Laravel 10 or 11 without a full rewrite.
- What kind of tenant isolation does this bundle provide?
- The overview says it provides tenant-aware configuration and isolation so multiple tenants can be served from one codebase. The exact isolation mechanisms depend on the bundle's configuration and your application setup. Review the repository source and docs to confirm how tenant context is resolved and applied. Do not assume it provides database-per-tenant isolation out of the box.
- Is syonix/multi-tenancy-bundle maintained?
- The repository is a legacy Symfony 2 bundle, and Symfony 2 is end-of-life, so active maintenance is unlikely. Check the GitHub repository for the latest commits, issues, and releases before adopting it. For new projects, choose a modern maintained tenancy package instead.
- What are alternatives to syonix/multi-tenancy-bundle for Laravel?
- Laravel developers should use Laravel-specific tenancy packages rather than a Symfony 2 bundle. Common options include stancl/tenancy and spatie/laravel-multitenancy, though you should evaluate their current support and fit. For Symfony, look for modern Symfony tenancy bundles or build tenant context into your application directly.
- How should I test multi-tenancy with syonix/multi-tenancy-bundle?
- Test tenant resolution and configuration isolation by booting the Symfony 2 kernel with different tenant contexts and asserting that each tenant sees only its expected config and data. Add integration tests around any shared services or request listeners the bundle provides. Because the bundle is legacy, also test on the exact PHP and Symfony 2 versions you deploy.
- Can I use syonix/multi-tenancy-bundle in production?
- It may be possible in a legacy Symfony 2 production app if you have audited the code, configuration, and security implications of tenant isolation. However, Symfony 2 is unsupported and the bundle appears legacy, so production use carries maintenance and security risk. Prefer a maintained tenancy solution for new or actively developed applications.
Weaver
How can I help you explore Laravel packages today?