- Is geeksltd/pangolin.symfony a Laravel package?
- No. geeksltd/pangolin.symfony is a Symfony bundle for the Pangolin multi-tenancy framework, consumed through Symfony bundle registration, DI compiler passes, and kernel boot. Laravel has no equivalent bundle mechanism, so it cannot be dropped into a Laravel app as-is. Direct fit with a Laravel estate is effectively zero without a bridge or standalone Symfony runtime.
- How do I install and configure Pangolin.Symfony?
- In a Symfony application, install it with Composer, register the bundle, and configure tenant resolution and Doctrine filters in bundle config. In Laravel, there is no bundle registration or Symfony kernel lifecycle to hook into. You would need a bridge layer, or run a minimal Symfony kernel as a separate HTTP or console service.
- What Laravel versions does Pangolin.Symfony support?
- None officially. The package is a Symfony bundle and does not declare Laravel support. If you attempt a bridge, you must validate its Symfony component constraints against the versions pinned by your Laravel release, because conflicts can surface as hard composer update failures.
- How does Pangolin for Symfony resolve tenants and scope Doctrine queries?
- It resolves the active tenant per request using host, subdomain, or a custom resolver, then scopes Doctrine queries through filters. That keeps most application code tenant-agnostic. Tenant-aware console commands and migrations are also part of the bundle's scope.
- What PHP and Symfony versions does Pangolin.Symfony require?
- The exact constraints are in the package's composer.json, which the overview does not state. The technical assessment flags a possible ceiling at PHP 8.1 and Symfony 5.4, which would block newer runtimes. Check composer.json and abandoned transitive dependencies before any commitment.
- Is Pangolin.Symfony actively maintained and safe for production?
- The repository shows 0 stars, 0 dependents, and a last release dated 2022-10-06, roughly three years stale. That means little third-party validation, no community to surface edge cases, and no realistic expectation of upstream fixes. Treat it as an unsupported vendor evaluation, not a production-ready library, unless Geeks Ltd offers commercial support.
- How do I test multi-tenancy with Pangolin.Symfony?
- Test it in a throwaway standalone Symfony project, not your Laravel monolith. Boot a minimal kernel with different tenant hosts or subdomains and assert that Doctrine filters scope query results correctly. Also cover tenant-aware console commands and migrations, and write your own tests because there is no upstream test signal to rely on.
- What are Laravel-native alternatives to Pangolin for multi-tenancy?
- Start with Laravel's first-party primitives such as actions, jobs, events, and policies, plus actively maintained Laravel multi-tenancy packages. The technical assessment is clear that mature Laravel-native options exist with larger install bases and active maintenance. The case for Pangolin must be a specific, evidenced capability gap, not a preference.
- How can I evaluate Pangolin.Symfony without migrating my Laravel app?
- Run a throwaway spike in a standalone Composer project pinned to the 2022 release, boot a minimal Symfony kernel, and exercise two or three representative use cases. Migrate nothing; the output should be a go/no-go memo. If it survives, put a single bounded context behind an interface your Laravel app already owns so the dependency stays swappable.
- What are the main production risks of adopting Pangolin.Symfony?
- Key risks are low adoption, a stale release, a bus factor of one, unknown license and test coverage, and possible PHP or Symfony version ceilings. Running it as a sidecar also adds a runtime to operate. Validate Composer constraints, transitive dependencies, and commercial support before committing.