Download the PHP package decodelabs/effigy without Composer
On this page you can find all versions of the php package decodelabs/effigy. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download decodelabs/effigy
More information about decodelabs/effigy
Files in decodelabs/effigy
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 effigy
Effigy
Universal CLI entry point
Effigy is a globally installed universal CLI tool for easily running tasks in your application.
Get news and updates on the DecodeLabs blog.
Installation
You will also need to have added your global composer installation bin directory to your $PATH in your ~/.bash_profile or ~/.bashrc file:
Note, earlier versions of composer may store global config in ~/.composer/vendor/bin - adapt your $PATH as necessary. You can find composer's home path with composer global config home
Usage
Effigy can be used to simplify running tasks in your project from the command line. Its primary job is to locate and load the main entry point to your project via a globally installed executable.
Say for example, you currently run commands in your project though webroot/index.php as your primary entry point:
Define your entry point in your composer.json file:
Then you can run CLI commands available in your project via the effigy executable directly:
Should you need per-environment entry files, specify template keys in your composer config:
Then on first run, Effigy will ask for the "env" parameter and save it in a local config file (which gets added to your .gitignore).
Local installation
If you don't want to install Effigy globally, you can use it as a local executable in your project.
You can then call effigy like so:
PHP binary
Effigy can use alternative versions of PHP on a per-project basis:
The bin path is stored in your local config and all process launches will use this going forward. Reset it to "php" to use the default system global binary.
Composer passthrough
Effigy will attempt to run scripts defined in your composer.json:
You can also run composer commands through effigy directly:
This is especially useful if you have defined an alternative version of PHP for your project as global composer will use global PHP.
Licensing
Effigy is licensed under the MIT License. See LICENSE for the full license text.
All versions of effigy with dependencies
composer-runtime-api Version ^2.2
decodelabs/archetype Version ^0.3
decodelabs/atlas Version ^0.12
decodelabs/clip Version ^0.3.2
decodelabs/dictum Version ^0.6
decodelabs/exceptional Version ^0.4
decodelabs/integra Version ^0.1.4
decodelabs/genesis Version ^0.9
decodelabs/lucid Version ^0.4.7
decodelabs/systemic Version ^0.11
decodelabs/terminus Version ^0.10.1
decodelabs/veneer Version ^0.11.6
symplify/easy-coding-standard Version ^12.1
php-parallel-lint/php-parallel-lint Version ^1.3
ondram/ci-detector Version ^4.1