Download the PHP package hatchyu/laravel-pipeline-engine without Composer

On this page you can find all versions of the php package hatchyu/laravel-pipeline-engine. 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?

Informations about the package laravel-pipeline-engine

Laravel Pipeline Engine

Latest Version on Packagist Total Downloads

[!WARNING] Disclaimer & Notice for Public Users: This package is primarily developed and tailored for the author's personal, client projects, and proprietary Laravel products. While it is open-source, it is highly opinionated to fit specific workflow requirements.

If you choose to use this package in your own environments, please review its behaviors and defaults carefully. Use it at your own discretion.

A reusable, configurable, and highly extensible CI/CD pipeline engine for Laravel projects. It provides centralized shell scripts for linting, security checking, and testing, along with a custom interactive Laravel Artisan installer command to configure GitHub Actions workflows in seconds.


🚀 Why Use Laravel Pipeline Engine?

Instead of copy-pasting hundreds of lines of GitHub Actions YAML configurations across all your Laravel projects, this package centralizes your pipeline logic in a single dependency.


📦 Installation

Install the package via Composer as a dev dependency:


🛠️ Getting Started

1. Run the Interactive Installer

Configure and scaffold your GitHub Actions workflow file by running:

This interactive CLI will guide you through:

  1. Selecting your PHP version.
  2. Enabling/disabling frontend/Node.js asset building.
  3. Deciding which checks (Quality, Security, Tests) to include in the pipeline.

The script creates/updates your .github/workflows/ci.yml file.

2. Push to GitHub

Commit the new workflow file and push to GitHub:


🔍 Core Runners

The package registers three binaries under vendor/bin/ which run automatically in CI, but can also be run locally:

1. vendor/bin/ci-lint

Checks code quality in three phases:

2. vendor/bin/ci-security

Ensures dependency safety:

3. vendor/bin/ci-test

Executes test suites seamlessly:


🎛️ Customizations & Overrides

Environment Overrides

If your project requires a specific database (e.g. MySQL) or special env configurations for testing, configure them directly in your .github/workflows/ci.yml file or your .env.testing. The runners respect existing environment variables:

Adding Project-Specific Pipeline Steps

Since the GitHub Actions file lives in your project repository, you can seamlessly add custom actions (e.g. E2E tests, build steps, or boundary assertions) directly alongside the core runners:

Running Tests in Parallel

If your application has a large test suite, you can run tests in parallel to speed up execution. The test runner automatically forwards arguments to the underlying testing tool (like Pest or Artisan):

Testing Multiple PHP/Laravel Versions (Matrix Build)

If you are developing a package or need to ensure compatibility across multiple PHP versions, you can modify the scaffolded .github/workflows/ci.yml file to use a GitHub Actions matrix:


📄 License

The MIT License (MIT). Please see License File for more information.


All versions of laravel-pipeline-engine with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
illuminate/support Version ^9.0|^10.0|^11.0|^12.0|^13.0
illuminate/console Version ^9.0|^10.0|^11.0|^12.0|^13.0
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 hatchyu/laravel-pipeline-engine contains the following files

Loading the files please wait ...