- Is tadcka/routing-bundle a Laravel package?
- No. It is a Symfony bundle that wraps the Symfony CMF Routing component for dynamic, database-backed route resolution. It assumes Symfony's DI container, AppKernel bundle registration, and Doctrine ORM/ODM or PHPCR persistence. None of that maps to Laravel's service provider or router pipeline.
- Can I install tadcka/routing-bundle in a Laravel application?
- Not as a native dependency. You would need a bespoke adapter, and the bundle's Symfony/CMF dependencies do not integrate with Laravel's router. For Laravel, reimplement the route-provider pattern against Laravel's RouteRegistrar or cached route collection instead.
- What Laravel versions does tadcka/routing-bundle support?
- None. It is a Symfony bundle, not a Laravel package, so there is no service provider, package discovery, or Laravel router integration. Use Laravel-native routing or a custom route provider for Laravel applications.
- What PHP and Symfony versions does this routing bundle require?
- It targets legacy Symfony 2.x/3.x and PHP 5.5 through 7.x. Modern PHP 8.x and Symfony 6/7 will almost certainly fail Composer resolution against its constraints. Expect blockers around PHP 8, Symfony 4+, PSR-11/PSR-6, and Doctrine ORM 2.x versus 3.x.
- Is tadcka/routing-bundle maintained and safe for production?
- The last release was 2016-10-05, making it roughly nine years stale, with 1 star and 0 dependents. There is no security patching, no PHP 8 compatibility, and the upstream Symfony CMF Routing component is itself in maintenance or abandoned status. Treat it as frozen and high-risk for production use.
- What does tadcka/routing-bundle actually do?
- It integrates the Symfony CMF Routing component to centralize route definitions and management. It provides route providers, route repositories, and route-aware content linking so routes can be resolved from a database-backed store rather than static files. That pattern supports dynamic URL structures with caching.
- How do I install and configure tadcka/routing-bundle?
- In a legacy Symfony application, install it via Composer, register the bundle in AppKernel, and configure route providers plus Doctrine ORM/ODM or PHPCR persistence. Do not install it in greenfield or modern codebases. Run an explicit composer.json constraint audit before committing.
- What are the Laravel alternatives for dynamic database-driven routing?
- Use Laravel's native routing with route model binding and cached route collections, or implement a custom route provider that loads routes from your database into the RouteRegistrar. For Symfony, evaluate maintained CMF RoutingBundle forks or Sylius resource routing. A custom provider is often only about 300 lines.
- Can I reimplement the route-provider pattern in Laravel?
- Yes. The transferable concept is resolving routes from a store at runtime and caching the resulting route collection. Implement it against Laravel's RouteRegistrar or Route collection and your existing persistence layer, typically in one to two sprints. Do not drag in CMF Routing and its transitive dependency tree.
- What are the security risks of DB-driven dynamic routing?
- If an admin or editor UI can create routes, you inherit injection and privilege-escalation vectors that no one is patching in an abandoned bundle. Also assess the blast radius if route resolution fails at request time, including 500 errors, SEO loss, and broken deep links. Vendor code only after verifying license and provenance.