Download the PHP package loadsys/puphpet-release-composer-installer without Composer

On this page you can find all versions of the php package loadsys/puphpet-release-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 puphpet-release-composer-installer

puphpet-release-composer-installer

Build Status

Provides a composer custom installer that works with loadsys/puphpet-release to add a PuPHPet.com vagrant box to a project via composer.

You probably will never need to use this project yourself directly. We use it for our loadsys/puphpet-release package to copy parts of the PuPHPet package into the necessary locations for the consuming project.

:warning: Big Important Warning

It's critically important to point out that this installer does things that composer very explicitly should not be doing. We break this very good and wise rule only because the tools we're working with (vagrant and puphpet) leave us with no other practical choice. Again: You should NOT do what this installer does. In all likelihood there is a better way.

If you use this installer, it will overwrite existing (important!) files in your project. If you have customized your Vagrantfile, then composer require a project that uses this installer, your Vagrantfile file and puphpet/ folder will be unceremoniously overwritten without notice. Do not complain about this. This is what this installer is designed to do and you've been duly warned of its danger.

Usage

To use this installer with another composer package, add the following block to your package's composer.json file:

Composer Post Install Actions

This installer is responsible for performing post-composer install actions for the loadsys/puphpet-release package.

When this package is included in another project via composer, the installer fires a number of additional actions in order to address some of the incompatibilities between puphpet's default setup and the requirements for Vagrant (such as the Vagrantfile living in the project's root directory instead of the composer-installed /vendors/loadsys/puphpet-release/release/ folder.)

Unresolved Questions:

Contributing

Running Unit Tests

Manually Testing Installer Output

Testing this composer plugin is difficult because it involves at least 2 other projects: the loadsys/puphpet-release, and the project from which you want to consume it. This project contains a tests/integration/ directory that is set up to exercise this installer and test the result of including the loadsys/puphpet-release package in a consumer project. To use it:

  1. Check out this project: git clone [email protected]:loadsys/puphpet-release-composer-installer.git

  2. Check out a copy of the puphpet-release project somewhere to work on it. git clone [email protected]:loadsys/puphpet-release.git (Make a note of this path.)

  3. Create a feature branch in either project, and commit your changes to the branch. (Committing the changes is very important to the process: Any changes you wish to test must exist in the git index already, not just in your working copy.)

  4. Run ./tests/integration/simulate-composer-install.sh

    The script will prompt you for any necessary information, reset the build/ dir for use, write the appropriate "composer.json" changes for you, and execute a composer install command for you in the build/ dir where you can review the results.

    • The build/ folder should end up with a Vagrantfile and puphpet/ folder in it.
    • The sample build/puphpet.yaml file should have been copied to build/puphpet/config.yaml.
    • The sample .gitignore file should have been "safely" updated to include the new additions to the "root" project folder (build/).
  5. From here, the process loops through the following steps:

    • Make changes to the puphpet-release or puphpet-release-composer-installer projects.
    • Commit the changes to your working branch.
    • Run ./tests/integration/simulate-composer-install.sh again.
    • Check the results in the build/ directory.
    • Repeat.
  6. Once you're satisfied with the results, push your branch and submit a PR.

Running Integration Tests

The simulation script also includes a number of functional tests for verifying the results of the installer's operation. Use the -t flag to enable them.

The script will report any errors and exit non-zero on failure.

License

MIT. In particular, all PuPHPet work belongs to the original authors. This project is strictly for our own convenience.

Copyright

© Loadsys Web Strategies 2015


All versions of puphpet-release-composer-installer with dependencies

PHP Build Version
Package Version
Requires composer-plugin-api Version 1.0.0
symfony/filesystem Version ~2.6
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 loadsys/puphpet-release-composer-installer contains the following files

Loading the files please wait ....