Download the PHP package phizzl/deployee without Composer
On this page you can find all versions of the php package phizzl/deployee. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 deployee
Deployee task runner
Setup
You can require deployee via composer
Configuration
Create a file called deployee.yml. You might copy it fom vendor/phizzl/deployee-cli/deployee.dist.yml.
Load specified configuration by an OS environment var
If you want to use another configuration you can change it by setting the environment variable DEPLOYEE_CONFIG with the absolute path to the configuration to use.
Load config by --env option
You also are able to load a configuration by defining the --env option
In the example above Deployee will try to read the configuration from a file called delpoyee.dev.yml in you current CWD.
Deployments
Tasks
There are several of tasks you can use to define your deployment. The functionality that makes it possible to define a deployment is stored in the Dpeloyment plugin. For more information see the documentation here
Filesystem
See documentation here
Shell
See documentation here
MySQL database
See documentation here
OXID eShop
See documentation here
Annotation controlled deployments
You can manipulate the behaviour of when a deplyoment is executed by setting annotations to the deployment definition. If you want to know more about how to force a deployment to run always or only when a specified environment is given take a look at the plugin docs here
Plugins
The system itself is designed to be event and plugin based. So the functionality to define a deployment is a plugin itself that adds events and commands to the system.
Create a new plugin
If you want to add functionality to Deployee you are able to create your own plugin. For this you need a Plugin class that extends the AbstractPlugin class.
After you defined your plugin you just have to add your class to your Deployee config YAML file under the plugin section.
Plugin configuration parameter
You can also define your plugin configuration in the config YAML file. This parameters will be available in the plugins initialize method.
Than you can access the config vars as in the following example
All versions of deployee with dependencies
symfony/event-dispatcher Version ^3.3
symfony/yaml Version ^3.3
symfony/finder Version ^3.3
symfony/console Version ^2.8
pimple/pimple Version ^3.0
monolog/monolog Version ^1.23
phizzl/php-mysql-command-builder Version ^0.2
phpdocumentor/reflection-docblock Version ^3.2