Download the PHP package loadsys/puphpet-release without Composer

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

puphpet-release

Makes an unpacked version of the vagrant environment generated by puphpet.com available via composer and Packagist.

This repo represents a snapshot of the PuPHPet project. It includes minimal tooling designed to fetch a copy of the PuPHPet release ZIP file and import it back into this project. This project includes a composer.json file, making it possible to include puphpet in another target project using composer.

There are a still a number of things that could stand to improve. For those, see:

:warning: Big Important Warning :warning:

This package uses a composer custom installer that does very non-standard, typically bad, things, including overwriting files in your project outside of the vendor/ directory.

This is something that composer very explicitly says we 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.

:exclamation: Using this package will cause any root level /Vagrantfile and /puphpet/ folder in your existing project to be unceremoniously overwritten without notice, and a /.gitignore to be created or modified. Do not complain about this. This is what this package is designed to do and you've been duly warned of its danger.

Requirements

Installation

Run the following command to include the vagrant environment provided by PuPHPet in your project:

Usage

Once you've included the package as instructed above, you should be able to run vagrant with the default configuration immediately:

Customizing

To customize the vagrant box, you have two choices:

or

In either case, your puphpet.yaml file should be committed to your own project's source control system so the vagrant virtual machine remains identical for all developers on the project.

@TODO: What about files/ and exec-* scripts?

Running the release scraper

This project includes a shell script designed to fetch the latest puphpet.zip file from puphpet.com, unpack it, and commit it back into this repo.

This script is intended be scheduled to run via cron to update the repo periodically. It must be run from a clone of the remote repo that Packagist is aware of and that has ssh permission to push back to the remote repository.

Packagist expects semantic versioning, and this presents a challenge. The puphpet.com project does not conform to semver and the project makes backwards-incompatible changes frequently. To work around this, the release script automatically tags each new version using a minor number. This allows consuming projects to target a specific point release that will never auto-update in a breaking way.

The consequence is that consuming projects must manually update their targeted version and verify it is still operational for their needs (as well as check that their puphpet.yaml file is up to date.)

Contributing

See the Contributing section of the loadsys/puphpet-release-composer-installer package for instructions on working with these two projects.

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 with dependencies

PHP Build Version
Package Version
Requires phpfu/puphpet-installer Version *
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 contains the following files

Loading the files please wait ....