Download the PHP package internal/dload without Composer

On this page you can find all versions of the php package internal/dload. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of internal/dload

Informations about the package dload

![DLoad](./resources/logo.svg)

Download artifacts easily

[![Support](https://img.shields.io/static/v1?style=flat-square&label=Support&message=%E2%9D%A4&logo=GitHub&color=%23fe0086)](https://patreon.com/roxblnfk)


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:

Table of Contents

Installation

PHP Latest Version on Packagist Total DLoads

Quick Start

  1. Install DLoad via Composer:

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

  1. Create your configuration file interactively:

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

  2. Download configured software:

  3. Integrate with Composer (optional):

Command Line Usage

Initialize Configuration

Download Software

Download Options

Option Description Default
--path Directory to store binaries Current directory
--arch Target architecture (amd64, arm64) System architecture
--os Target OS (linux, darwin, windows) Current OS
--stability Release stability (stable, beta) stable
--config Path to configuration file ./dload.xml
--force, -f Force download even if binary exists false

View Software

Build Custom Software

Build Options

Option Description Default
--config Path to configuration file ./dload.xml

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:

This will:

Manual Configuration

Create dload.xml in your project root:

Download Types

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

Type Attribute

Default Behavior (No Type Specified)

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

Explicit Type Behaviors

Type Behavior Use Case
binary Binary checking, version validation, executable permissions CLI tools, executables
phar Downloads .phar files as executables without unpacking PHP tools like Psalm, PHPStan
archive Forces unpacking even for .phar files When you need archive contents

[!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:

Advanced Configuration Options

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

Velox Action Attributes

Attribute Description
velox-version Version constraint for the Velox build tool to use
golang-version Go version constraint required for building RoadRunner
roadrunner-ref RoadRunner Git reference (tag, commit, or branch) to use as the base for building
config-file Path to base configuration file that may be merged with remote API responses or other sources
binary-path Output path for the built RoadRunner binary. File extension is automatically added based on OS (.exe for Windows). Defaults to current working directory
debug Build RoadRunner with debug symbols to profile it with pprof (boolean, defaults to false)

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:

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

DLoad Configuration

Building RoadRunner

Custom Software Registry

Defining Software

Software Elements

Repository Configuration

Binary Elements

File Elements

Use Cases

Development Environment Setup

New Project Setup

CI/CD Integration

Cross-Platform Teams

Each developer gets the correct binaries for their system:

PHAR Tools Management

Frontend Asset Distribution

GitHub API Rate Limits

Use a personal access token to avoid rate limits:

Add to CI/CD environment variables for automated downloads.

Contributing

Contributions welcome! Submit Pull Requests to:

All versions of dload with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
composer/semver Version ^3.4
nyholm/psr7 Version ^1.8
psr/container Version 1 - 2
psr/http-client Version ^1.0
react/async Version ^3.2 || ^4.3
react/promise Version ^2.10 || ^3.2
symfony/console Version ^6.4 || ^7
symfony/http-client Version ^4.4 || ^5.4 || ^6.4 || ^7
yiisoft/injector Version ^1.2
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package internal/dload contains the following files

Loading the files please wait ....