Weave Code
Be Simple Deployment Bundle Laravel Package
ibrows/be-simple-deployment-bundle
The Ibrows Simple Deployment Bundle for Symfony offers a lightweight way to configure and trigger deployment tasks from your application, reducing manual steps and keeping routine releases simple, repeatable, and easy to manage with minimal setup.
At a glance
Frequently asked questions about Be Simple Deployment Bundle
- Can I use ibrows/be-simple-deployment-bundle in a Laravel application?
- No. It is a Symfony2 bundle that registers into the Symfony Kernel and depends on FrameworkBundle conventions, DI compiler passes, and Bundle lifecycle behavior. Laravel has no bundle loader and no Kernel::registerBundles() concept. There is no supported integration path.
- Is be-simple-deployment-bundle compatible with Laravel 10 or 11?
- No. The bundle targets Symfony 2.x-era dependency constraints, which conflict with the modern symfony/console and symfony/process versions Laravel 10 and 11 require. A composer require in a current Laravel app will almost certainly fail at dependency resolution. That failure is expected and prevents an accidental production dependency.
- What Laravel version does this package support?
- None. It supports Symfony2 applications, not Laravel. Symfony2 has been end-of-life since November 2018, with earlier 2.x releases EOL even sooner. There is no Laravel version compatibility.
- Why does composer require fail for this package in a Laravel project?
- The package pins Symfony 2.x-era constraints that cannot be resolved alongside the Symfony components Laravel needs. Composer cannot produce a consistent dependency set. This is a feature, not a bug, because it blocks an unsupported and risky install.
- What is the Laravel equivalent of be-simple-deployment-bundle?
- Laravel Envoy covers scripted remote tasks over SSH using Blade-style syntax. Deployer with the Laravel recipe covers atomic releases, rollback, and multi-host deploys. Laravel Forge, Vapor, or container rollouts cover managed deployment, and GitHub Actions or GitLab CI can orchestrate any of them.
- Is ibrows/be-simple-deployment-bundle actively maintained?
- There is no meaningful maintenance signal. The repository has zero stars, zero dependents, and a score of zero, indicating no community validation or adoption. It targets a dead framework generation, so treat it as dormant.
- Is it safe to use this deployment bundle in production?
- High risk. Deployment code is the most privileged code you run because it holds SSH keys and production credentials. A dormant, zero-dependent, PHP 5.x-era package in that position is the worst place to accumulate unpatched debt, and it will fail composer audit and supply-chain gates.
- Does be-simple-deployment-bundle work with Symfony 5, 6, or 7?
- No. It is built for Symfony2 only and relies on that generation's bundle structure and dependency constraints. Modern Symfony releases use different conventions and component versions. There is no supported upgrade path from this bundle to current Symfony.
- Can I fork be-simple-deployment-bundle and port it to Laravel?
- Not advisable. Forking means you own a privileged deploy tool and must provide a named maintainer, a patch SLA, and a security-response commitment. The functional equivalent is already covered better by Laravel Envoy, Deployer, or CI-driven deploys. That budget is better spent elsewhere.
- What deployment approach should Laravel teams use instead?
- Define your actual requirements first: atomic releases, rollback, multi-node fan-out, zero-downtime, and secrets handling. Then use Laravel Envoy or Deployer for scripted deploys, Forge or Vapor for managed deployments, and CI pipelines for orchestration. Avoid porting Symfony2 bundles; buy or build against the requirement list instead.
Weaver
How can I help you explore Laravel packages today?