- What does ongr/connections-bundle do?
- It is a Symfony bundle for configuring and managing Elasticsearch connections in the ONGR ecosystem. It supports multiple named connections and exposes services for accessing clients through Symfony's dependency injection container. Its value is mostly Symfony bundle and DI wiring, not framework-agnostic Laravel code.
- Is ongr/connections-bundle a Laravel package?
- No. It is a Symfony 2-era bundle built around bundle registration, DI extensions, YAML config trees, and compiler passes, none of which Laravel consumes. There is no Laravel service provider, facade, or publishable config in the package.
- Can I install ongr/connections-bundle in Laravel 10 or 11?
- Realistically no. The archived 2015 release targets PHP 5.x and Symfony 2.x components, so Composer dependency resolution will normally fail against Laravel 10/11 with PHP 8.1/8.2 and Symfony 6/7 transitive dependencies. Using --ignore-platform-reqs is a red flag and does not make the bundle Laravel-compatible.
- Which Laravel versions support ongr/connections-bundle?
- None are supported. The package predates modern Laravel and was built for Symfony kernels rather than Laravel's service-provider and config model. There is no compatibility matrix for Laravel 8, 9, 10, 11, or newer.
- Why is ongr/connections-bundle deprecated?
- The repository is archived and the package is marked deprecated, with the overview directing users to use an API instead. It was last shipped in 2015, has essentially no users or dependents, and has no maintenance path. Symfony 2 is EOL, so the underlying assumptions are obsolete.
- Does ongr/connections-bundle support Elasticsearch 7 or 8?
- There is no evidence of support for modern Elasticsearch versions. The bundle is from the ONGR Elasticsearch ecosystem of the Symfony 2 era and likely assumes Elasticsearch 1.x/2.x client behavior. For Elasticsearch 7 or 8 in Laravel, use a maintained client or Laravel Scout integration instead.
- How do I manage multiple Elasticsearch connections in Laravel without this bundle?
- Create a Laravel-native connection manager or bind named Elasticsearch client instances in a service provider. Put connection definitions in config/connections.php or config/elasticsearch.php, resolve them with config(), and expose a small interface rather than depending on archived bundle classes. This gives you idiomatic config caching, testing hooks, and container bindings.
- Can I use ongr/connections-bundle as a design reference for a Laravel implementation?
- Yes, but only as a reference. Its useful ideas are a named-connection registry and a thin abstraction over client creation; the Symfony DI wiring should be discarded and reimplemented with a service provider and config file. Do not make the archived package a runtime dependency.
- Is ongr/connections-bundle safe for production Laravel applications?
- No. It is archived, unmaintained, untested against modern PHP, and has no security advisory or CVE response path. Adopting it creates an immediate fork and ownership obligation. For production, use maintained Elasticsearch clients and Laravel-native integration.
- What are alternatives to ongr/connections-bundle for Laravel?
- Use a maintained Elasticsearch PHP client directly, Laravel Scout with an Elasticsearch driver, or a small in-house connection manager bound in a service provider. If you need multiple named connections, implement that registry in Laravel rather than trying to bridge a Symfony bundle. Check the ONGR Elasticsearch bundle lineage for maintained successors, but do not assume Laravel compatibility.