Weave Code
Hosting Laravel Package
21torr/hosting
21torr/hosting is a small Symfony bundle providing essential tools for hosting Symfony-based applications, helping streamline deployment and operations with basic hosting utilities and sensible defaults.
Base bundle for hosting any Symfony-based application.
Frequently asked questions about Hosting
- Is 21torr/hosting compatible with Laravel?
- 21torr/hosting is a Symfony bundle and has no native Laravel support. A Laravel app would need Symfony container and console integration, such as a bridge, plus custom wrappers for hooks and health checks. For a pure Laravel project, native Laravel alternatives are usually simpler and safer.
- Can I install 21torr/hosting in a Laravel application?
- You can add it with Composer, but installing it does not make it a Laravel package. It expects Symfony bundle registration and Symfony services, so a Laravel app needs a bridge or manual container setup. Without that integration, its commands and health checks will not work as intended.
- What PHP and Symfony versions does 21torr/hosting require?
- The bundle is Symfony-centric and targets Symfony 7 or later, with PHP 8.4 or later. That makes it unsuitable for older Laravel stacks without polyfills or upgrades. Check your Laravel version's PHP support before considering it.
- How do build and deploy hooks work in 21torr/hosting?
- It uses BuildHookInterface and DeployHookInterface for extensible build and deployment steps. In Symfony these fit naturally into the container and console workflow. In Laravel you would need to adapt them to service providers, events, or Artisan commands, which is not provided out of the box.
- Does 21torr/hosting provide health checks for Kubernetes or uptime monitoring?
- It includes live and ready health check infrastructure, which can map to Kubernetes probes or uptime monitoring. The implementation is Symfony-oriented and would require custom Laravel work. For Laravel, spatie/laravel-health or custom endpoints are more direct options.
- What changed in 21torr/hosting 4.0 and is migration required?
- Version 4.0.0 changed the config key from hosting to 21torr_hosting and deprecated some interfaces. Existing users must update configuration and replace deprecated interfaces during migration. Treat it as a breaking upgrade and test hooks and health checks afterward.
- What are Laravel-friendly alternatives to 21torr/hosting?
- For deployment hooks, evaluate deployer/deployer or laravel/envoy. For health checks, spatie/laravel-health or custom Laravel endpoints are more native. For build metadata, Laravel config values or parsing composer.json may be enough.
- Is 21torr/hosting production-ready for a Laravel project?
- It has limited adoption, with zero stars and zero dependents noted in the assessment, so stability is unproven. It also lacks Laravel-specific guides, which raises integration and maintenance risk. Use it only after a proof of concept and with a clear reason to add Symfony components.
- How would I prototype 21torr/hosting in Laravel?
- Start with a small proof of concept that integrates only HostingEnvironment and bridges Symfony's container to Laravel. Then adapt build hooks to service providers or events and replace Doctrine health checks with Laravel checks. Expect several weeks of work before core features are reliable.
- How do I handle build metadata with 21torr/hosting in Laravel?
- The bundle collects event-based build info such as Git tags and timestamps. Laravel apps can store similar metadata in config or a cache/database entry without the bundle. If you need the bundle's granularity, you will need custom integration with Laravel's events and configuration.
Weaver
How can I help you explore Laravel packages today?