Weave Code
Blt Laravel Package
blumilksoftware/blt
BLT is Blumilk's Laravel starter template for quickly scaffolding modern PHP web apps. It ships with Docker-based local development, preconfigured code quality and testing tools, and sensible defaults so teams can start building features right away.
Behat+Laravel toolbox. Still in progress.
Frequently asked questions about Blt
- What is blumilksoftware/blt?
- blumilksoftware/blt is Blumilk's opinionated Laravel starter template for scaffolding modern PHP web applications, not a runtime library you add as a dependency. It bundles Docker-based local development, preconfigured code quality and testing tools, and default conventions. The Composer description also calls it a Behat+Laravel toolbox and notes that it is still in progress, so evaluate it as a project scaffold rather than a production runtime package.
- How do I start a new Laravel project with blt?
- Adopt it by scaffolding a new repository from the template, then pin to a tagged release rather than a branch. The assessment recommends confirming that the PHP and Laravel 13 combination is actually exercised in CI before standardizing on v1.1.0. If that is not confirmed, scaffold from v1.0.0 and backport the CI hardening you need.
- Does blt support Laravel 13?
- v1.1.0 moves the template's baseline to Laravel 13 and widens the Laravel constraint, so support is declared. The important caveat is that declaring support is not the same as validated support. Check whether the test matrix actually runs against Laravel 13 or merely permits it in composer.json before treating it as a validated baseline.
- Is blt still compatible with Laravel 12?
- The constraint can allow Laravel 12 and 13, but that does not guarantee the Laravel 12 path is still actively tested. Widening the constraint can mask failures because a Laravel 12 consumer may receive a template version whose tooling assumptions target Laravel 13. Confirm the tested matrix and support policy before relying on Laravel 12.
- Can I use blt in an existing Laravel application?
- The realistic path for an existing application is selective backporting, not a wholesale re-template. The CI workflow hardening is a self-contained, portable artifact that can be lifted into any repository. Evaluate the widened Laravel 13 constraint on its own timeline and avoid re-templating an established codebase.
- What CI changes are included in blt v1.1.0?
- The release includes a hardened GitHub Actions workflow with explicit minimum permissions and actions pinned by SHA. That change is portable to other repositories regardless of framework version. Because it was authored by a first-time automated contributor, human review of PR #87 is advisable before adopting it.
- How should I maintain SHA-pinned GitHub Actions in blt?
- SHA pinning reduces supply-chain risk but creates a maintenance burden because pinned SHAs go stale silently. Configure Dependabot or Renovate, or assign a human owner to rotate the pins. If you fork blt as an internal standard, own the CI workflow and treat upstream as an input rather than the source of truth.
- What PHP version does blt v1.1.0 require?
- The provided release information does not state the minimum PHP version for v1.1.0. Before adopting it, inspect composer.json and the CI matrix to see whether it forces a PHP upgrade alongside Laravel 13. That check matters for both greenfield scaffolds and any backport into existing repositories.
- Is blt ready for production use?
- Treat blt as a starter template for new projects, not as a drop-in runtime dependency for production services. The package is described as still in progress, and the assessment flags open questions about Laravel 13 validation, PHP requirements, release cadence, and support windows. Review the CI change and confirm the full PHP, Laravel, tooling, and package compatibility matrix before committing.
- What are alternatives to blt for Laravel scaffolding?
- Compare blt with Laravel's official starter kits or your organization's established internal scaffold. blt is a strong fit only if you want Blumilk's bundled conventions, including Docker development, static analysis, code style, and frontend tooling. Teams with an existing scaffold or conflicting platform standards should avoid adopting blt wholesale.
Weaver
How can I help you explore Laravel packages today?