Download the PHP package ysato/catalyst without Composer

On this page you can find all versions of the php package ysato/catalyst. 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 catalyst

Ysato.Catalyst

A scaffolding tool to accelerate the setup of Laravel projects.

About This Package

This package generates the necessary file structure for initializing a Laravel project using a unified template system with enhanced extensibility.

Important Note: This command will always overwrite existing files. To prevent unintended changes, you are expected to carefully review the output with a tool like git diff after running the command, and then selectively commit only the changes you want to adopt.

The tool's role is to generate a diff based on the latest template; how that diff is handled is delegated to the user.

Installation

Prerequisites (Strongly Recommended)

This package strongly recommends installing just, a command runner that simplifies Docker-based development workflows.

Please refer to the installation guide for your platform. For example, on macOS with Homebrew:

Package Installation

Run the following command to install:

Usage

This command will prompt you for necessary information interactively when run without arguments. For automation, you can pass the information as arguments to run it non-interactively.

Interactive Execution

If you run the command without any arguments, you will be prompted sequentially for the vendor name, package name, and PHP version.

Execution with Arguments (for Automation)

For use in CI/CD scripts, you can run the command non-interactively by passing arguments in the following format.

Format:

Argument Description
<vendor> (Required) The vendor name for namespacing (e.g., Ysato).
<package> (Required) The package name that follows the vendor (e.g., Catalyst).
<php> (Required) The PHP version to configure for the project (e.g., 8.3).

Example:

Options

Option Description
--with-ca-file (Optional) Path to a custom CA certificate file to trust within the container. Needed when behind a corporate proxy.

Example with Arguments and Options:

Post-Setup Manual Steps

Initial QA Setup

When running just composer lints for the first time on a newly scaffolded project, you may encounter errors due to existing code patterns. To resolve these, create baseline files for each QA tool:

PHP_CodeSniffer Baseline

PHPMD Baseline

PHPStan Baseline

Add the generated baseline file to the includes in phpstan.neon:

Psalm Baseline

Laravel IDE Helper Setup

For enhanced IDE support and autocompletion, run the Laravel IDE Helper commands:

OpenAPI Validation in Feature Tests

This package provides two types of OpenAPI validation capabilities for Feature tests:

Place your OpenAPI specification at the project root as openapi.yaml, or configure the path via OPENAPI_SPEC_PATH environment variable.

1. Request/Response Validation (ValidatesOpenApiSpec)

Automatically validates that requests called from test cases and returned responses comply with the OpenAPI specification.

2. Specification Coverage Verification (Spectatable)

Verifies whether the specifications described in the OpenAPI specification are being called from tests.

This displays a report showing which endpoints and status codes have been tested:

Importing GitHub Rulesets

This project generates predefined GitHub rulesets as JSON files in the .github/rulesets directory. These must be manually applied to your repository.

Prerequisites

Importing via GitHub UI

  1. Navigate to your repository on GitHub.
  2. Click on Settings.
  3. In the left sidebar, under the "Code and automation" section, click on Rules, then Rulesets.
  4. Click the "Import ruleset" button.
  5. When prompted to upload a JSON file, select a .json file from the .github/rulesets/ directory.
  6. Review the imported settings and click "Create".
  7. Repeat for other ruleset files as needed.

    Note: Carefully review the "Target branches" section for each ruleset after import to ensure they apply to the intended branches (e.g., main, develop).

Documentation

Detailed documentation is available on the GitHub wiki.

For Contributors

Development Setup

This project uses Docker for development. Use the provided justfile commands.

Available Commands

Compatibility Testing

To install the oldest compatible versions of dependencies and ensure this package works reliably in diverse environments, run the following command:

License

This package is provided under the MIT License.


All versions of catalyst with dependencies

PHP Build Version
Package Version
Requires php Version ~8.2.27 || ~8.3.16 || ~8.4.3
barryvdh/laravel-ide-helper Version ^3.5
composer/composer Version ^2.6
digitalrevolution/php-codesniffer-baseline Version >=1.0.0
doctrine/coding-standard Version >=10.0.0
illuminate/console Version ^11.43 || ^12.0
illuminate/support Version ^11.43 || ^12.0
kirschbaum-development/laravel-openapi-validator Version ^1.1.1
larastan/larastan Version ^3.0
laravel/prompts Version ^0.3.5
phpmd/phpmd Version >=2.12.0
phpunit/phpunit Version ^10.5 || ^11.0 || ^12.0.1
psalm/plugin-laravel Version ^3.0
spatie/temporary-directory Version ^2.2
squizlabs/php_codesniffer Version >=3.7.1
symfony/filesystem Version ^7.1
symfony/finder Version ^7.1
twig/twig Version ^3.20
vimeo/psalm Version >=6.12.0
ysato/spectator Version ^1.1.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 ysato/catalyst contains the following files

Loading the files please wait ...