Download the PHP package monofone/ansible-installer without Composer
On this page you can find all versions of the php package monofone/ansible-installer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download monofone/ansible-installer
More information about monofone/ansible-installer
Files in monofone/ansible-installer
Package ansible-installer
Short Description Installer for ansible roles
License MIT
Homepage http://github.com/monofone/ansible-installer/
FAQ
Example:
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 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.
Informations about the package ansible-installer
Ansible Installer
This is originally taken form the composer/installers and adapted to work as an ansible role installer.
This is for PHP package authors to require in their composer.json. It will
install their package to the correct location based on the specified package
type.
The goal of installers is to be a simple package type to install path map.
Users can also customize the install path per package and package authors can
modify the package name upon installing.
Current Supported Package Types:
Stable types are marked as bold, this means that installation paths for those type will not be changed. Any adjustment for those types would require creation of brand new type that will cover required changes.
| Framework | Types |
|---|---|
| ansible | ansible-role |
Example composer.json File
This is an example for a ansible role. The only important parts to set in your
composer.json file are "type": "ansible-role" which describes what your
package is and "require": { "ansible/installer": "~1.0" } which tells composer
to load the custom installers.
This would install your role to the provisioning/roles/common/ folder when a
user runs php composer.phar install.
Custom Install Paths
If you are consuming a package that uses the ansible/installer you can
override the install path with the following extra in your composer.json:
A package type can have a custom installation path with a type: prefix.
This would use your custom path for each of the listed packages. The available
variables to use in your paths are: {$name}, {$vendor}, {$type}.
Custom Install Names
If you're a package author and need your package to be named differently when
installed consider using the installer-name extra.
For example you have a package named you/mysql with the type
ansible-role. Installing with ansible/installer would install to the
path provisioning/roles/mysql. Due to the strict naming conventions, you as a
package author actually need the package to be named and installed to
provisioning/roles/ownmysql. Using the following config within your package composer.json
will allow this:
Please note the name entered into installer-name will be the final and will
not be inflected.
