Download the PHP package scafera/scaffold without Composer

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

Informations about the package scaffold

scafera/scaffold

Composer plugin that scaffolds framework-owned files into Scafera projects.

Provides: Composer plugin that copies framework-owned files (entry point, kernel bootstrap, .gitignore, config examples) into Scafera projects on composer install/update. Files are always overwritten (except initial-files, copied once) to keep framework and project in sync.

Depends on: Composer 2+ (composer-plugin-api ^2.0). Activates automatically for any installed package that declares extra.scafera-scaffold.

Extension points:

  • composer.json → extra.scafera-scaffold.files — logical keys mapped to source paths in the declaring package; always overwritten on install
  • extra.scafera-scaffold.initial-files — literal target paths; copied once, never overwritten (intended for user-editable configs)
  • extra.scafera-scaffold.target-map — architecture packages remap logical keys to project-specific paths (e.g. index.php → public/index.php)
  • extra.scafera-scaffold.file-mapping — project-level opt-out ("public/index.php": false to disable a scaffolded file)
  • Convention — package-side scaffold sources live under support/scaffold/ at the package root

Not responsible for: Code generation (use scafera make:controller, make:service, make:command from the architecture package — e.g. scafera/layered) · application scaffolding (only framework-owned files are copied) · modifying user-authored code · conflict resolution beyond last-package-wins for duplicate logical keys.

How It Works

Scafera packages declare which files they provide. The plugin collects these declarations from all installed packages and copies the files into the project.

Package Declaration

Packages declare scaffold files in their composer.json under extra.scafera-scaffold.

files — Always Overwritten

Use a logical key (not a path) to identify each file. The key decouples the file identity from its target location.

The logical key is used as the default target path. To place the file elsewhere, an architecture package provides a target-map (see below).

initial-files — Created Once

Files that are only copied if the target does not already exist. Useful for configuration files that the developer is expected to modify.

Unlike files, initial files use literal target paths (not logical keys).

target-map — Control Placement

Architecture packages can remap where a logical key is placed without duplicating the source file.

This tells the plugin: place the file identified by index.php at public/index.php. The source remains in the kernel — no duplication.

A different architecture package could remap the same key:

Project-Level Overrides

Projects can disable specific scaffolded files via file-mapping:

Disabled files are skipped during scaffolding with a console message.

File Placement Convention

Packages that provide scaffold files should place them under support/scaffold/ at the package root:

Conflict Resolution

If multiple packages declare the same logical key, the last package processed wins. Package order is determined by Composer's dependency resolution.

Console Output

The plugin logs every action during scaffolding:

Requirements

License

MIT

All versions of scaffold with dependencies

PHP Build Version
Package Version
Requires php Version >=8.4
composer-plugin-api Version ^2.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 scafera/scaffold contains the following files

Loading the files please wait ...