Dload Laravel Package

Product Decisions This Supports

• Developer Experience (DX) Enhancement:

  • Automate binary tooling setup (e.g., RoadRunner, Temporal, CLI tools) to reduce onboarding friction for engineers.
  • Eliminate manual curl/wget scripts or hardcoded paths in CI/CD pipelines, improving maintainability.
  • Roadmap: Prioritize projects requiring consistent tooling (e.g., microservices, event-driven architectures).

• Build vs. Buy:

  • Buy: Avoid reinventing binary distribution logic (e.g., custom scripts, Ansible roles).
  • Build: Extend the package for internal tooling (e.g., custom software registry, private binaries) if open-source limitations exist.

• Use Cases:

  • CI/CD Optimization: Replace flaky post-install scripts with declarative dload.xml configurations.
  • Cross-Platform Teams: Standardize tool versions across Linux/Windows/macOS environments.
  • PHAR/Asset Management: Distribute frontend assets (e.g., Node.js binaries, Docker CLI) alongside PHP code.
  • Custom RoadRunner: Build tailored binaries with specific plugins (e.g., Temporal + KV store) without manual Go builds.

• Security/Compliance:

  • Enforce version pinning (e.g., ^2025.1.0) to mitigate supply-chain risks in binary dependencies.
  • Roadmap: Add checksum validation or signed artifact support for critical tools.

When to Consider This Package

• Adopt if:

  • Your PHP project relies on external binaries (e.g., RoadRunner, Temporal, CLI tools) with version consistency needs.
  • You manage multi-platform teams (Windows/Linux/macOS) and want to avoid manual setup steps.
  • CI/CD pipelines currently use ad-hoc scripts (e.g., Bash, PowerShell) to fetch binaries.
  • You need to distribute non-PHP assets (e.g., frontend tooling, Docker binaries) alongside code.
  • Developer onboarding is slow due to missing tooling (e.g., "install RoadRunner first").

• Look elsewhere if:

  • Your binaries are trivial (e.g., single curl-able files) and don’t require versioning/extraction.
  • You use containerized environments (Docker/Kubernetes) where binaries are pre-installed.
  • Your team prefers manual control over tooling (e.g., "let developers handle their own installs").
  • You need enterprise-grade features (e.g., proxy caching, air-gapped deployments) not covered by the BSD-3 license.
  • Your binaries are proprietary and require custom authentication (e.g., private GitHub repos).

How to Pitch It (Stakeholders)

For Executives:

*"DLoad solves a critical pain point in PHP development: consistent, automated setup of binary tools like RoadRunner or Temporal. Today, engineers waste time manually installing tools or debugging broken CI pipelines due to missing binaries. This package:

• Reduces onboarding time by 30–50% with zero-touch tooling setup.
• Eliminates flaky CI/CD jobs caused by inconsistent binary versions.
• Future-proofs our stack by supporting custom RoadRunner builds and cross-platform teams. For $0 cost (BSD-3 license), we gain enterprise-grade tooling distribution—comparable to npm’s node-gyp or Go’s go install."

For Engineering:

*"DLoad replaces fragile curl | bash scripts with a declarative, maintainable way to manage binaries:

• Composer integration: Add dload get to post-update-cmd for automatic setup.
• Cross-platform: Works on Linux/Windows/macOS without platform-specific hacks.
• Extensible: Supports custom software registries, PHAR tools, and even RoadRunner plugin builds. Example: Replace your install-tools.sh with a dload.xml config—no more ‘works on my machine’ issues."*

For DevOps/SRE:

*"This package standardizes binary distribution in CI/CD:

• Pin versions (e.g., rr:^2025.1.0) to avoid supply-chain risks.
• Integrates with GitLab CI (sample config provided) for reproducible builds.
• Reduces pipeline complexity by consolidating binary fetches into one step. Use case: Add dload get to your before_script to ensure all jobs start with the same tooling."*