Dload Laravel Package

DLoad simplifies downloading and managing binary artifacts for your projects. Perfect for development environments that require specific tools like RoadRunner, Temporal, or custom binaries.

Why DLoad?

DLoad solves a common problem in PHP projects: how to distribute and install necessary binary tools and assets alongside your PHP code. With DLoad, you can:

• Automatically download required tools during project initialization
• Ensure all team members use the same versions of tools
• Simplify onboarding by automating environment setup
• Manage cross-platform compatibility without manual configuration
• Keep binaries and assets separate from your version control

Table of Contents

• Installation
• Quick Start
• Command Line Usage
  • Initialize Configuration
  • Download Software
  • View Software
  • Build Custom Software
• Configuration Guide
  • Interactive Configuration
  • Manual Configuration
  • Download Types
  • Version Constraints
  • Advanced Configuration Options
• Building Custom RoadRunner
  • Build Action Configuration
  • Velox Action Attributes
  • Build Process
  • Configuration File Generation
  • Using Downloaded Velox
  • DLoad Configuration
  • Building RoadRunner
• Custom Software Registry
  • Defining Software
  • Software Elements
• Use Cases
  • Development Environment Setup
  • New Project Setup
  • CI/CD Integration
  • Cross-Platform Teams
  • PHAR Tools Management
  • Frontend Asset Distribution
• API Rate Limits
• Gitlab CI configuration
• Contributing

Installation

composer require internal/dload -W

Quick Start

1. Install DLoad via Composer:

   composer require internal/dload -W
   

Alternatively, you can download the latest release from GitHub releases.

2. Create your configuration file interactively:

   ./vendor/bin/dload init
   

   This command will guide you through selecting software packages and create a dload.xml configuration file. You can also create it manually:

   <?xml version="1.0"?>
   <dload xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/php-internal/dload/refs/heads/1.x/dload.xsd"
   >
      <actions>
          <download software="rr" version="^2025.1.0"/>
          <download software="temporal" version="^1.3"/>
      </actions>
   </dload>
   

3. Download configured software:

   ./vendor/bin/dload get
   

4. Integrate with Composer (optional):

   {
       "scripts": {
           "post-update-cmd": "dload get --no-interaction -v || \"echo can't dload binaries\""
       }
   }
   

Command Line Usage

Initialize Configuration

# Create configuration file interactively
./vendor/bin/dload init

# Create configuration in specific location
./vendor/bin/dload init --config=./custom-dload.xml

# Create minimal configuration without prompts
./vendor/bin/dload init --no-interaction

# Overwrite existing configuration without confirmation
./vendor/bin/dload init --overwrite

Download Software

# Download from configuration file
./vendor/bin/dload get

# Download specific packages
./vendor/bin/dload get rr temporal

# Download with specific versions and minimum stability
./vendor/bin/dload get rr:2025.* dolt:1.44.1 mago:1.*@alpha

# Download with options
./vendor/bin/dload get rr --stability=beta --force

Download Options

View Software

# List available software packages
./vendor/bin/dload software

# Show downloaded software
./vendor/bin/dload show

# Show specific software details
./vendor/bin/dload show rr

# Show all software (downloaded and available)
./vendor/bin/dload show --all

Build Custom Software

# Build custom software using configuration file
./vendor/bin/dload build

# Build with specific configuration file
./vendor/bin/dload build --config=./custom-dload.xml

Build Options

The build command executes build actions defined in your configuration file, such as creating custom RoadRunner binaries with specific plugins. For detailed information about building custom RoadRunner, see the Building Custom RoadRunner section.

Configuration Guide

Interactive Configuration

The easiest way to create a configuration file is using the interactive init command:

./vendor/bin/dload init

This will:

• Guide you through selecting software packages
• Show available software with descriptions and repositories
• Generate a properly formatted dload.xml file with schema validation
• Handle existing configuration files gracefully

Manual Configuration

Create dload.xml in your project root:

<?xml version="1.0"?>
<dload xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/php-internal/dload/refs/heads/1.x/dload.xsd"
       temp-dir="./runtime">
    <actions>
        <download software="rr" version="^2025.1" />
        <download software="temporal" />
        <download software="frontend" extract-path="frontend" />
    </actions>
</dload>

Download Types

DLoad supports three download types that determine how assets are processed:

Type Attribute

<!-- Explicit type specification -->
<download software="psalm" type="phar" />        <!-- Download .phar without unpacking -->
<download software="frontend" type="archive" />  <!-- Force archive extraction -->
<download software="rr" type="binary" />         <!-- Binary-specific processing -->

<!-- Automatic type handling (recommended) -->
<download software="rr" />           <!-- Uses all available handlers -->
<download software="frontend" />     <!-- Smart processing based on software config -->

Default Behavior (No Type Specified)

When type is not specified, DLoad automatically uses all available handlers:

• Binary processing: If software has <binary> section, performs binary presence and version checking
• Files processing: If software has <file> section and asset is downloaded, processes files during unpacking
• Simple download: If no sections exist, downloads asset without unpacking

<!-- registry list -->
<software name="complex-tool">
    <binary name="tool" pattern="/^tool-.*/" />
    <file pattern="/^config\..*/" extract-path="config" />
</software>

<!-- actions list -->
<!-- Uses both binary and files processing -->
<download software="complex-tool" />

Explicit Type Behaviors

[!NOTE] Use type="phar" for PHP tools that should remain as .phar files. Using type="archive" will unpack even .phar archives.

Version Constraints

Use Composer-style version constraints:

<actions>
    <!-- Exact version -->
    <download software="rr" version="2.12.3" />
    
    <!-- Range constraints -->
    <download software="temporal" version="^1.20.0" />
    <download software="dolt" version="~0.50.0" />
    
    <!-- Stability constraints -->
    <download software="tool" version="^1.0.0@beta" />
    
    <!-- Feature releases (automatically sets preview stability) -->
    <download software="experimental" version="^1.0.0-experimental" />
</actions>

Advanced Configuration Options

<dload temp-dir="./runtime">
    <actions>
        <!-- Different extraction paths -->
        <download software="frontend" extract-path="public/assets" />
        <download software="config" extract-path="config" />
        
        <!-- Target different environments -->
        <download software="prod-tool" version="^2.0.0@stable" />
        <download software="dev-tool" version="^2.0.0@beta" />
    </actions>
</dload>

Building Custom RoadRunner

DLoad supports building custom RoadRunner binaries using the Velox build tool. This is useful when you need RoadRunner with custom plugin combinations that aren't available in pre-built releases.

Build Action Configuration

<actions>
    <!-- Basic configuration using local velox.toml -->
    <velox config-file="./velox.toml" />

    <!-- With specific versions -->
    <velox config-file="./velox.toml"
           velox-version="2025.1.1"
           golang-version="^1.22"
           roadrunner-ref="v2025.1.2"
           binary-path="./bin/rr"
           debug="true" />

    <!-- Custom plugins -->
    <velox>
        <plugin name="temporal" />
        <plugin name="kv" />
    </velox>
</actions>

Velox Action Attributes

Build Process

DLoad automatically handles the build process:

1. Golang Check: Verifies Go is installed globally (required dependency)
2. Velox Preparation: Uses Velox from global installation, local download, or downloads automatically if needed
3. Configuration: Copies your local velox.toml to build directory
4. Building: Executes vx build command with specified configuration
5. Installation: Moves built binary to target location and sets executable permissions
6. Cleanup: Removes temporary build files

[!NOTE] DLoad requires Go (Golang) to be installed globally on your system. It does not download or manage Go installations.

Configuration File Generation

You can generate a velox.toml configuration file using the online builder at https://build.roadrunner.dev/

For detailed documentation on Velox configuration options and examples, visit https://docs.roadrunner.dev/docs/customization/build

This web interface helps you select plugins and generates the appropriate configuration for your custom RoadRunner build.

Using Downloaded Velox

You can download Velox as part of your build process instead of relying on a globally installed version:

<actions>
    <download software="velox" extract-path="bin" version="2025.1.1" />
    <velox config-file="velox.toml"
          golang-version="^1.22"
          roadrunner-ref="2024.1.5" />
</actions>

This ensures consistent Velox versions across different environments and team members.

DLoad Configuration

<?xml version="1.0"?>
<dload xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/php-internal/dload/refs/heads/1.x/dload.xsd">
    <actions>
        <velox config-file="./velox.toml" 
              velox-version="^1.4.0"
              golang-version="^1.22"
              roadrunner-ref="2024.1.5"
              binary-path="./bin/rr" />
    </actions>
</dload>

Building RoadRunner

# Build RoadRunner using velox.toml configuration
./vendor/bin/dload build

# Build with specific configuration file
./vendor/bin/dload build --config=custom-rr.xml

Custom Software Registry

Defining Software

<dload>
    <registry overwrite="false">
        <!-- Binary executable -->
        <software name="RoadRunner" alias="rr" 
                  homepage="https://roadrunner.dev"
                  description="High performance Application server">
            <repository type="github" uri="roadrunner-server/roadrunner" asset-pattern="/^roadrunner-.*/" />
            <binary name="rr" pattern="/^roadrunner-.*/" />
        </software>

        <!-- Archive with files -->
        <software name="frontend" description="Frontend assets">
            <repository type="github" uri="my-org/frontend" asset-pattern="/^artifacts.*/" />
            <file pattern="/^.*\.js$/" />
            <file pattern="/^.*\.css$/" />
        </software>

        <!-- Mixed: binaries + files -->
        <software name="development-suite" description="Complete development tools">
            <repository type="github" uri="my-org/dev-tools" />
            <binary name="cli-tool" pattern="/^cli-tool.*/" />
            <file pattern="/^config\.yml$/" extract-path="config" />
            <file pattern="/^templates\/.*/" extract-path="templates" />
        </software>

        <!-- PHAR tools -->
        <software name="psalm" description="Static analysis tool">
            <repository type="github" uri="vimeo/psalm" />
            <binary name="psalm.phar" pattern="/^psalm\.phar$/" />
        </software>
        
        <!-- GitLab repository -->
        <software name="My cool project" alias="cool-project"
              homepage="https://gitlab.com/path/to/my/repository"
              description="">
            <repository type="gitlab" uri="path/to/my/repository" asset-pattern="/^cool-.*/" />
            <binary name="cool" pattern="/^cool-.*/" />
        </software>
    </registry>
</dload>

Software Elements

Repository Configuration

• type: Currently supports "github"
• uri: Repository path (e.g., "username/repo")
• asset-pattern: Regex pattern to match release assets

Binary Elements

• name: Binary name for reference
• pattern: Regex pattern to match binary in assets
• Automatically handles OS/architecture filtering

File Elements

• pattern: Regex pattern to match files
• extract-path: Optional extraction directory
• Works on any system (no OS/architecture filtering)

Use Cases

Development Environment Setup

# One-time setup for new developers
composer install
./vendor/bin/dload init  # First time only
./vendor/bin/dload get

New Project Setup

# Start a new project with DLoad
composer init
composer require internal/dload -W
./vendor/bin/dload init
./vendor/bin/dload get

CI/CD Integration

# GitHub Actions
- name: Download tools
  run: GITHUB_TOKEN=${{ secrets.GITHUB_TOKEN }} ./vendor/bin/dload get

Cross-Platform Teams

Each developer gets the correct binaries for their system:

<actions>
    <download software="rr" />        <!-- Linux binary for Linux, Windows .exe for Windows -->
    <download software="temporal" />   <!-- macOS binary for macOS, etc. -->
</actions>

PHAR Tools Management

<actions>
    <!-- Download as executable .phar files -->
    <download software="psalm" type="phar" />
    <download software="phpstan" type="phar" />
    
    <!-- Extract contents instead -->
    <download software="psalm" type="archive" />  <!-- Unpacks psalm.phar -->
</actions>

Frontend Asset Distribution

<software name="ui-kit">
    <repository type="github" uri="company/ui-components" />
    <file pattern="/^dist\/.*/" extract-path="public/components" />
</software>

<actions>
    <download software="ui-kit" type="archive" />
</actions>

API Rate Limits

Use a personal access token to avoid rate limits:

GITHUB_TOKEN=your_token_here ./vendor/bin/dload get
GITLAB_TOKEN=your_token_here ./vendor/bin/dload get

Add to CI/CD environment variables for automated downloads.

Gitlab CI configuration

When you make a release in Gitlab, make sure to upload your assets to the release page via package manager. This can easily be done via Gitlab CLI and the glab release upload --use-package-registry command.

# .gitlab-ci.yml

Build artifacts:
  stage: push
  script:
    - mkdir bin
    - echo "Mock binary for darwin arm" > bin/cool-darwin-arm64
    - echo "Mock binary for darwin amd" > bin/cool-darwin-amd64
    - echo "Mock binary for linux arm" > bin/cool-linux-arm64
    - echo "Mock binary for linux amd" > bin/cool-linux-amd64
  artifacts:
    expire_in: 2 hours
    paths:
      - $CI_PROJECT_DIR/bin/cool-*
  rules:
    - if: $CI_COMMIT_TAG

Release artifacts:
    stage: deploy
    image: gitlab/glab:latest
    needs: [ "Build artifacts" ]
    script:
        - glab auth login --job-token $CI_JOB_TOKEN --hostname $CI_SERVER_HOST
        - glab release upload --use-package-registry "$CI_COMMIT_TAG" ./bin/*
    rules:
        - if: $CI_COMMIT_TAG

Contributing

Contributions welcome! Submit Pull Requests to:

• Add new software to the predefined registry
• Improve DLoad functionality
• Enhance documentation and translate this on other languages