Weave Code
Pomm Symfony Bridge Laravel Package
pomm-project/pomm-symfony-bridge
Symfony bundle bridging Pomm (PostgreSQL Object Model Manager) into Symfony apps. Provides DI integration, configuration and service setup to access Pomm sessions and database connections cleanly from your Symfony services.
Pomm2 shared elements for profiler between Silex and Symfony.
Frequently asked questions about Pomm Symfony Bridge
- Can I use this package in a Laravel project for PostgreSQL profiling with Pomm2?
- No, this package is designed exclusively for Symfony/Silex. Laravel lacks native Symfony profiler support, so you’d need a workaround like a Symfony microservice or a custom Laravel Debugbar integration. Evaluate Laravel Debugbar or Tideways as alternatives.
- What Laravel alternatives exist for profiling Pomm2 PostgreSQL queries?
- For Laravel, consider Laravel Debugbar (with custom Pomm2 listeners) or Tideways for profiling. If you’re using PostgreSQL, Pomm2’s built-in profiler can log data to a file or service, which you could then parse in Laravel. Avoid framework lock-in by abstracting profiling logic.
- Is this package compatible with Laravel 10 and PHP 8.2?
- No, this package targets Symfony/Silex and is abandoned (last release: 2020). It won’t work directly in Laravel, and compatibility with PHP 8.2+ or Laravel 10 is untested. If you must use it, isolate it in a Symfony microservice or fork it for Laravel.
- How do I install this in a Symfony app using Pomm2?
- This package is auto-installed via `pomm-project/pomm-bundle` (Symfony) or `pomm-project/pomm-profiler-service-provider` (Silex). Avoid manual installation unless you’re extending its functionality. Ensure Symfony 5.x/6.x and PHP 7.4+ are used for compatibility.
- Will this add significant performance overhead in production?
- Yes, profiling adds runtime overhead. Disable it in production by configuring Symfony’s profiler to run only in `dev` environments. Test with realistic query loads to measure impact, especially if using Pomm2’s caching or complex queries.
- Can I use this package alongside Laravel via API or microservices?
- Yes, you could deploy a Symfony microservice (e.g., using Laravel Horizon or Encore) to host the profiler, then expose its data via an API for Laravel consumption. This avoids direct framework conflicts but adds architectural complexity.
- Does this package support PostgreSQL connection pooling or advanced Pomm2 features?
- This bridge focuses on Symfony profiler integration, not Pomm2’s core features like connection pooling. Ensure your Pomm2 setup (e.g., `pomm-project/pomm`) handles pooling separately. The bridge only exposes profiling data to Symfony’s Web Profiler.
- How do I test this package in a CI/CD pipeline for Symfony?
- Use Symfony’s built-in test tools (e.g., PHPUnit with Symfony’s Kernel) to mock the profiler. Test Pomm2 queries in isolation, then verify profiler data appears in the Web Profiler. Avoid testing in production-like environments unless profiling is enabled.
- What happens if I upgrade Symfony but this package is abandoned?
- Since the package is unmaintained, upgrades may break compatibility. Monitor Symfony’s deprecations and consider forking it if critical. Alternatively, migrate to Laravel Debugbar or Tideways, which are actively maintained for Laravel’s ecosystem.
- Can I profile specific Pomm2 operations (e.g., caching, transactions) with this?
- Yes, the bridge exposes Pomm2’s profiler data to Symfony’s Web Profiler, including queries, caching, and transactions. Configure Pomm2’s profiler to log the operations you need, then filter them in Symfony’s profiler UI or API.
Weaver
How can I help you explore Laravel packages today?