- What is devio/permalink used for in Laravel?
- devio/permalink is a Laravel-specific, database-driven routing layer for editable permalinks and SEO parameters. It fits content-managed URLs such as marketing pages, CMS entries, landing pages, localized slugs, and multi-site SEO paths without redeploying route files. It is a poor fit for core application or API routing, high-volume transactional paths, and non-Laravel services.
- How do I install devio/permalink with Composer?
- Install it with Composer using the package name devio/permalink, then follow the package's migration and configuration publishing steps from its documentation. Because the provided README excerpt is empty, confirm the exact service-provider, config, and table setup before integrating. Start in a non-production branch and verify autoloading and database driver support.
- Is devio/permalink compatible with Laravel 10 or Laravel 11?
- The provided assessment does not confirm support for Laravel 10 or 11. The last release was 2020-12-17, so treat modern Laravel compatibility as unverified and test against your exact Laravel and PHP stack before adoption. Check the package Composer constraints and run a non-production spike.
- Does devio/permalink work with Laravel route caching?
- Route-cache behavior is a flagged technical risk. A database-driven routing layer can bypass Laravel's cached route table, so verify route:cache behavior, middleware ordering, and 404 handling in a spike. Keep a static-route fallback or kill switch if you adopt it.
- How does devio/permalink handle slug collisions and redirects?
- The assessment flags slug-collision handling and redirect and canonical correctness as risks, not as proven built-in guarantees. Model uniqueness, reserved paths, status codes, canonical URLs, and 410 and 404 cases explicitly in your permalink schema. Add contract tests for these cases before cutover.
- Can I use devio/permalink for multi-language or multi-tenant sites?
- The package is positioned for content-managed SEO paths, including localized slugs and multi-site paths, but the assessment warns that localization and multi-tenant scoping complicate middleware and resolution. Add explicit locale and tenant fields to the permalink model and test redirect, canonical, and 404 behavior per site. Do not assume built-in tenant isolation.
- Is devio/permalink production-ready and actively maintained?
- Treat it as a narrow, useful pattern rather than a broadly validated dependency: the last release was 2020-12-17, it has 65 stars, zero dependents, and an opportunity score of 0.44. For critical routing, vendor or fork it under an internal namespace with a named maintainer. MIT licensing reduces legal risk but not maintenance ownership.
- How should I cache database-driven permalink resolution?
- Database-driven resolution can add per-request overhead, so the assessment recommends caching aggressively and invalidating correctly across web nodes. Include a cache version in the permalink table and define invalidation on publish, redirect, and tenant or locale changes. Provide a fallback static-route map or kill switch if the database or permalink cache is unavailable.
- What are alternatives to devio/permalink for database-driven Laravel routing?
- The provided assessment does not name specific alternative packages. Viable approaches include Laravel native routes with CMS-managed slugs, a custom database-backed route resolver, or exposing resolved URLs from a content service API. Prefer a maintained option with clear ownership if this sits on a critical path.
- What testing should I do before adopting devio/permalink?
- Run a non-production spike against your exact Laravel and PHP version, including route:cache and middleware priority checks. Add contract tests for resolution, redirects, slug collisions, trailing slashes, casing, URL encoding, and 404 and 410 handling. Shadow-run dual resolution against current routes before enabling by route cohort with rollback flags.