Download the PHP package wireframe-framework/processwire-composer-installer without Composer

On this page you can find all versions of the php package wireframe-framework/processwire-composer-installer. 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 processwire-composer-installer

ProcessWire Composer Installer

This project contains Composer custom installers for ProcessWire CMS/CMF modules and site profiles.

What does it do and why do we need it?

By default Composer installs all packages into the /vendor/ directory. This is great for things that support this type of structure, but not so great for projects – such as ProcessWire – that expect things to be in specific location: modules in /site/modules/module-name/, and site profiles generally as the /site/ directory itself, /site-profile-name/ when the system hasn't been installed yet, or before installat/site-subsite-name/ in the case of native multisite support.

ProcessWire Composer Installer currently makes two "corrections" to packages that define it as a dependency in their composer.json files:

Site-specific modules supports

One more thing to note is that modules can be installed either from the root directory of the ProcessWire installation, or from the /site/ directory itself. Installer will automatically determine which location you're currently in, and adjust paths accordingly.

This way we can install modules on a per-site basis (in the case of multisite), or include Composer based module dependencies with a site profile (which would otherwise require manual modifications to the ProcessWire root directory composer.json file, or at least running composer require in the root directory for said dependencies.)

Alternatively...

There's a very similar project you might've heard of, called hari/pw-module. While this project and Hari's ProcessWire module installer are similar, there are a few key differences:

Usage

For developers installing modules or site profiles

Note that in order for this work, the module or site profile in question has to have wireframe-framework/processwire-composer-installer as a dependency. See next section for instructions for module or site profile authors.

Customizing installer paths

By default site profiles are installed under current working directory, and modules under site/modules/ (or modules/ in case you're already in a site directory). You can, though, override the default paths in the root composer.json of your project:

For module or site profile authors

The usage of this project is rather simple. You just need to a) add wireframe-framework/processwire-composer-installer as a dependency to your project by manually modifying the composer.json file or by running composer require wireframe-framework/processwire-composer-installer in your module or site profile root directory, and b) define the type of your package (via composer.json) as pw-module (for modules) or pw-site-profile (for site profiles).

Here's a stripped-down sample composer.json for a module:

And here's an equally stripped-down sample composer.json for a site profile:

In order for your modules to be easily installed, you should also add them to Packagist: https://packagist.org/.

Requirements

Why does this project require other installers via composer.json?

In case you're wondering why we currently have hari/pw-module as a requirement for this package, there's actually a good reason for this, even though it is admittedly a bit of a hack:

By adding other installers (currently only hari/pw-module) as a dependency for this project we're actually effectively forcing Composer to install it before this project, which in turn allows us to override other installers when it comes to choosing an installer for pw-* packages.

License

This project is licensed under the Mozilla Public License Version 2.0.

All versions of processwire-composer-installer with dependencies

PHP Build Version
Package Version
Requires composer-plugin-api Version ^1.0 || ^2.0
hari/pw-module Version ^1.0.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 wireframe-framework/processwire-composer-installer contains the following files

Loading the files please wait ....