Weave Code
Shorty Bundle Laravel Package
rezzza/shorty-bundle
Rezzza ShortyBundle integrates the Shorty URL shortener with Symfony applications. It provides configurable shortener services and Twig helpers so you can generate and display shortened links from controllers, services, or templates, making it useful for marketing links, sharing, and redirect-friend...
Underwear for your long urls in Symfony
Frequently asked questions about Shorty Bundle
- Can I use rezzza/shorty-bundle in a Laravel application?
- No. Rezzza ShortyBundle is a Symfony bundle built around Symfony 2-era dependency injection, configuration, and routing, and it does not provide a Laravel service provider, facade, or config file. Installing it in Laravel would give you Symfony bundle glue that Laravel will not register or boot. Treat it as reference material rather than a Laravel dependency.
- What Laravel versions does rezzza/shorty-bundle support?
- None. The package is a Symfony bundle, not a Laravel package, and the last release was in December 2015. There is no documented Laravel support for any version, including current Laravel 10 or 11. If you need URL shortening in Laravel, use a Laravel-native package or a small internal adapter.
- Is rezzza/shorty-bundle still maintained?
- No. The last release date is 2015-12-18, it has roughly 7 stars and 0 Packagist dependents, so there is no active downstream community testing compatibility for you. That means no security patching path and no guarantee that its provider clients still authenticate today. For production work, assume you would need to fork and own it.
- How do I install rezzza/shorty-bundle?
- On a legacy Symfony 2.3 to 2.8 application you would add it with Composer and register the bundle in AppKernel, but modern PHP and Symfony constraints will likely block dependency resolution. You may need platform requirement overrides just to resolve a fork. Do not expect a clean install on Symfony 5, 6, or 7, and do not expect Laravel auto-discovery.
- Does ShortyBundle call a third-party API or store short links itself?
- The overview describes pluggable URL-shortening providers plus a route and controller for resolving short codes, but the supplied material does not confirm whether storage is local or delegated to an external API. That distinction matters because a third-party API integration and a self-hosted redirect table are completely different operational problems. Inspect the repository's provider client and persistence layer before assuming either model.
- Which URL shortener providers does ShortyBundle support?
- The package advertises configurable, pluggable shortening providers, but the provided documentation excerpt does not enumerate them. Any provider client baked into a 2015 bundle is risky because Bitly moved from v3 to v4 with OAuth2 bearer tokens and Google's goo.gl shortener was shut down. Verify the current authentication scheme directly with the provider, not through the bundle.
- Does ShortyBundle work with Symfony 5, 6, or 7?
- It is very unlikely to work without a fork. The bundle sits in the Symfony 2.3 to 2.8 window, using XML or YAML service definitions, parameters, and ContainerAware-style wiring that modern Symfony has removed or retyped. A straight install will probably fail dependency resolution or container compilation. If your estate is frozen on Symfony 2.8 or 3.x it may technically run, but otherwise reimplement the seam.
- What should Laravel developers use instead of ShortyBundle?
- Build a thin internal abstraction with methods such as shorten and expand, then implement one adapter for a supported SaaS such as Bitly, Dub, or Short.io using Laravel's HTTP client. Add a storage concern only if you need to own the short-to-long mapping and redirect route. This is comparable effort to forking the bundle and leaves you with an interface you control.
- Is ShortyBundle safe for production or an abandoned dependency risk?
- Treat it as an abandoned dependency. It will show up in Composer audit and software composition analysis scans, has no security patch path, and uses credential-handling patterns that predate modern secrets management. The dominant technical risk is provider drift, since shortener APIs have changed sharply since 2015. If you must use it, fork it into an internal namespace and replace its HTTP layer before production.
- How do I migrate existing short links from ShortyBundle to Laravel?
- First inventory short links already in the wild in emails, SMS, print, and QR codes, then keep the existing redirect route and mapping table alive during migration. Next define your own LinkShortenerInterface and implement it against a modern provider or a self-hosted adapter using Laravel's HTTP client, with contract tests against the live provider. Budget roughly 3 to 5 engineer-days for a fork-and-harden path, but building thin is usually the better long-term choice.
Weaver
How can I help you explore Laravel packages today?