Download the PHP package jeffersongoncalves/laravel-zero-cli without Composer

On this page you can find all versions of the php package jeffersongoncalves/laravel-zero-cli. 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-zero-cli

Laravel Zero CLI

Scaffold a new Laravel Zero CLI project with the whole release pipeline already wired: PHAR build, self-update, git-cliff changelog, CI, and the conventions shared by the 16 *-cli projects in this account.

Built with Laravel Zero. Designed to be driven non-interactively (by an AI agent or a script) — every input is an argument or a flag, so there are no prompts.

Installation

Or grab the standalone PHAR from the latest release.

Usage

That writes a project whose composer install && composer test passes out of the box, with a deps executable, and prints the remaining steps (create the repo, run the release workflow, submit to Packagist).

Arguments

Argument Required Description
vendor-repo yes vendor/repo slug, e.g. jeffersongoncalves/deps-cli
description no Short one-line description, used in composer.json and the generated README.md

Options

Option Description
--binary=NAME Name of the executable. Default: the repo without its -cli suffix (deps-cli → deps), since the suffix names the project, not the command people type
--app-name="Name" Display name for config/app.php. Default: derived from the binary (deps → Deps CLI)
--path=DIR Target directory. Default: ./<repo> under the current directory
--author="Name" Author for composer.json and LICENSE. Default: git config user.name
--email=EMAIL Author email. Default: git config user.email
--no-git Skip git init and the first commit
--dry-run Print the planned file list without writing anything

What it generates

Laravel Zero skeleton, parameterized by the binary name:

<binary> (executable stub) · bootstrap/app.php · bootstrap/providers.php · config/app.php · config/commands.php · app/Providers/AppServiceProvider.php · app/Commands/SelfUpdateCommand.php · app/Commands/ExampleCommand.php

Build and release furniture:

box.json · cliff.toml · version.txt · .github/workflows/release.yml

Quality gates and meta:

phpstan.neon.dist · phpunit.xml.dist · tests/ · run-tests.yml · phpstan.yml · fix-php-code-style-issues.yml · dependabot.yml · SECURITY.md · LICENSE · CHANGELOG.md · README.md · .editorconfig · .gitattributes · .gitignore

The last group comes from laravel-zero-package-scaffold, shared with laravel-package-cli and filament-plugin-cli.

Why these files

Audited across the 16 existing *-cli repos before writing the templates:

Observation What it means
bootstrap/app.php and tests/TestCase.php — identical in all 16 Pure boilerplate, nothing to decide
release.yml, SelfUpdateCommand, AppServiceProvider, config/app.php — 16 "variants" One template, one substitution: the binary name
phpstan.neon.dist — 7 different contents across the only 8 repos that had one Drift, plus half the projects had no static analysis at all
box.json (3), cliff.toml (4), phpunit.xml.dist (5) Drift with no cause
jeffersongoncalves/laravel-zero-self-update — required by all 16 Part of the standard, wired in from the start

Every generated project therefore ships with static analysis, tests, and the same release flow — the things that were previously missing or subtly different from repo to repo.

The release invariant

The generated release.yml builds the PHAR and commits it to main before creating the tag, then pins the tag to that exact commit. Nothing rebuilds onto a post-tag commit, so a published tag never moves and Composer's stable-version immutability holds.

Updating

Testing

Changelog

Please see CHANGELOG for more information on what has changed recently.

Security

If you discover any security related issues, please see SECURITY.

License

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

All versions of laravel-zero-cli with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
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 jeffersongoncalves/laravel-zero-cli contains the following files

Loading the files please wait ...