Weave Code
Multiplex Bundle Laravel Package
liip/multiplex-bundle
LiipMultiplexBundle lets a Symfony project serve multiple applications or websites from one codebase, routing requests by host or configuration so each app can keep separate settings and templates while sharing common logic.
[DEPRECATED] Symfony2 controller that allows calling multiple URL's in one request as well as JSON-ifying any controller
Frequently asked questions about Multiplex Bundle
- Is liip/multiplex-bundle compatible with Laravel?
- No. LiipMultiplexBundle is a Symfony 2.x bundle built around the Symfony DI container and HttpKernelInterface, and it has no Laravel service provider or extension contract. Its Composer constraints pin Symfony 2.x, which conflicts with the Symfony 6.x/7.x ranges required by modern illuminate packages. Treat it as prior art for API composition, not as a Laravel dependency.
- Can I install liip/multiplex-bundle with Composer in a Laravel app?
- Composer installation will fail dependency resolution in a current Laravel project because the bundle requires Symfony 2.x components. Even if forced, a Laravel kernel would not boot the bundle's Symfony bundle extension or listeners. The practical path is to read the source and reimplement the batching idea with Laravel-native primitives.
- What is LiipMultiplexBundle used for?
- It is a deprecated Symfony2 controller and bundle that allowed one inbound request to call multiple URLs and return a composed response, and it could coerce any controller return value into JSON. It also supported serving multiple applications or sites from one codebase by routing on host or configuration. In Laravel terms, those ideas map to a custom batch endpoint and native JSON resources or response middleware.
- How do I batch multiple API calls in one Laravel request?
- Use Illuminate\Http\Client\Pool or Http::pool() to fan out concurrent downstream calls and capture per-request errors, then return a composed payload with per-item status codes. Avoid internal sub-request dispatch that re-enters the Laravel kernel unless you have proven it is safe for your middleware stack. Design the endpoint contract around partial failure so one failed item does not blank the whole response.
- Which Laravel versions support liip/multiplex-bundle?
- None. The package targets Symfony 2.x and PHP 5.x/7.0-era syntax, so it does not support Laravel 8, 9, 10, 11, or any modern Symfony version. There is no compatibility layer or maintained fork to bridge it.
- Is liip/multiplex-bundle maintained or tested?
- No. The repository is archived and deprecated, has roughly 12 stars, zero Packagist dependents, no maintainer, and no trustworthy CI or test suite against modern PHP. Symfony 2.8 reached end of life in November 2018, so any transitive dependencies inherit an unpatched CVE tail.
- Is it safe to run liip/multiplex-bundle in production?
- No. Running it in production would mean shipping unsupported Symfony 2.x code on the hot path of every aggregated request, with no security patch channel and a bus factor of one. The risk is contained only if you cite the source as a design reference and do not adopt the dependency.
- What are Laravel alternatives to liip/multiplex-bundle for JSON responses?
- Laravel already covers uniform JSON output with JsonResource, Responsable, response middleware, and standard array or JSON responses from controllers. For batch endpoints, a custom controller plus Http::pool() is the closer analogue to the bundle's multiplexing idea. You do not need this package to standardize response shapes.
- How do I serve multiple applications or websites from one Laravel codebase like this bundle?
- Laravel does not ship Symfony bundle-style host routing for separate applications in one codebase; you would typically use route groups with domain constraints, separate service providers or config namespaces, and per-app view namespaces. If the goal is multiple sites, evaluate a native Laravel multi-tenant or domain-routing structure rather than forcing a Symfony 2.x bundle.
- Should I depend on liip/multiplex-bundle or reimplement its pattern?
- Reimplement the pattern. Keep two ideas: a batch endpoint that returns per-item statuses, and a consistent JSON envelope enforced by Laravel responses or middleware. Record the decision explicitly so future engineers do not re-evaluate the archived repository as a dependency.
Weaver
How can I help you explore Laravel packages today?