Weave Code
Redirect Bundle Laravel Package
enhavo/redirect-bundle
Enhavo Redirect Bundle is a subtree split of the Enhavo CMS, an open-source PHP project built on the full-stack Symfony framework for flexible, complex data structures. See the main repository for full documentation and details.
EnhavoRedirectBundle
Frequently asked questions about Redirect Bundle
- Is enhavo/redirect-bundle a Laravel package?
- No. It is a Symfony bundle extracted as a subtree split from the Enhavo CMS monorepo and depends on Symfony's DI container, Doctrine ORM, and Enhavo's resource, metadata, and routing abstractions. It has no Illuminate service provider, Eloquent model, or Laravel-compatible middleware, so in a Laravel codebase it is best treated as a reference implementation rather than a dependency.
- Can I install enhavo/redirect-bundle in a Laravel application with Composer?
- Not realistically. A direct composer require would pull in symfony/framework-bundle, Doctrine, and Enhavo core packages, effectively bringing the CMS stack into your application. There is no Laravel integration layer, so you would be fighting the Symfony kernel and bundle assumptions rather than adding a redirect feature.
- Which Laravel and PHP versions does enhavo/redirect-bundle support?
- It does not target Laravel at all, so there is no Laravel version support to check. PHP and Symfony version compatibility must be confirmed from the main Enhavo repository because this subtree split has almost no documentation of its own. If you plan to port the logic, confirm PHP version parity first, since that is usually the only hard blocker.
- What redirect matching semantics does enhavo/redirect-bundle use?
- The README is essentially a logo and a pointer to the main repository, with no published behavior contract. The domain surface appears to be a redirect entity with source, target, status code, enabled flag, and optional domain or locale scope, plus a request listener that resolves an inbound path. It is not documented whether matching is exact path, prefix, wildcard, or regex, nor what precedence applies when multiple rules match. Define those semantics explicitly before porting anything.
- How does enhavo/redirect-bundle handle redirect chains and loops?
- Chain-following and cycle detection are not documented in the bundle. Redirect logic is deceptively subtle, and an undocumented reference carries real behavioral risk around multi-hop rules and accidental loops. If you port it, implement explicit cycle detection and a hard hop limit in your Laravel middleware.
- Does the bundle preserve query strings and URL fragments on redirect?
- This is not specified in the available documentation. Query strings and fragments are common sources of redirect bugs, especially when rules are written against paths only. Treat preservation, merging, and dropping as decisions you must make and test in your own implementation.
- How is redirect lookup cached and invalidated in enhavo/redirect-bundle?
- The README does not describe caching or invalidation behavior. In Enhavo it likely integrates with the CMS and Symfony stack rather than exposing a documented cache contract. For a Laravel port, use a cached full redirect map in Redis or the array cache, invalidate deterministically on writes, and warm the map during deployment.
- How do I migrate Enhavo redirects to a Laravel redirects table?
- Extract the entity fields you need, typically source, target, status code, enabled, and optional domain or locale scope, then create a fresh Eloquent schema. Doctrine annotations or attributes do not translate to Eloquent, and Enhavo's resource and metadata layer has no Laravel analog, so the admin UI must be rebuilt regardless. Build a CSV or legacy-table importer, backfill existing redirects, and run shadow-mode comparisons before cutover.
- What is a Laravel-native alternative to enhavo/redirect-bundle?
- Implement a redirects table with an Eloquent model, a global middleware or Route::fallback that looks up the inbound path, and a cached full-map for fast resolution. Add a Filament or Nova CRUD screen for editors and a CSV importer for legacy data. The Symfony bundle is useful mainly as a small spec for the entity shape and request-listener flow.
- Is enhavo/redirect-bundle actively maintained and safe for production?
- Adoption signals are essentially absent: zero stars, zero dependents, and a readme-level maturity marker. It is a read-only subtree split, so issues and pull requests live in the main Enhavo repository and release tags may not be mirrored. The MIT license means you can vendor or fork it if needed, but operationally you own the maintenance and should periodically review the monorepo for behavior changes.
Weaver
How can I help you explore Laravel packages today?