Download the PHP package rrb/deployer-bundle without Composer
On this page you can find all versions of the php package rrb/deployer-bundle. 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 deployer-bundle
Deployer Bundle
This is a Symfony bundle to deploy to multiple hosts at once using the git strategy. It provides commands to do it easily.
Each host may have independent configuration, i.e., you may want to checkout a development branch in your staging server, whereas you may want the master branch in your production server.
By default, the bundle only checkouts a specific version (either a tag or no) and clears the cache, but there are optional tasks that may also be executed. The order of execution is:
- checkout version
- composer update (if set)
- assets install (if set)
- database migrations (if set)
- cache clear
Installation
Step 0: Install fabric
This bundle uses Fabric to connect to hosts and execute tasks on them. You usually install it via pip:
Check fabric installation chapter for further information about installation.
Step 1: Download the Bundle
Open a command console, enter your project directory and execute the following command to download the latest stable version of this bundle:
This command requires you to have Composer installed globally, as explained in the installation chapter of the Composer documentation.
Step 2: Enable the Bundle
Then, enable the bundle by adding it to the list of registered bundles
in the app/AppKernel.php file of your project:
Step 3: Configure the Bundle
This bundle requires a minimal configuration in order to work (you
have to tell it where to deploy, right?), so you have to enable and
configure it in your config.yml file. This is the minimal configuration
that you require:
You may have as many hosts as you want. Check the configuration reference to know more about all available configuration options.
By default, fabric forwards the ssh-agent, so it is better if you deploy
using RSA keys. But, of course, there is the option of connect using
a password: just remember to add it to your parameters.yml file and
use its value in your config.yml file. Never commit your passwords!
See the commands reference for deploying.
Commands
Deploy
It will deploy to the last commit of the branch set in config.yml file. Deploy will always be sequential.
You may deploy to all hosts:
You may deploy to only one host
...or to a list of hosts, but not all:
If no host is specified, first host defined will be used:
is the same as executing:
You may also force a task execution besides deploy, overriding the default configuration:
Check the command reference to know all available
options. Options supplied to command take precedence over the ones
defined in the config.yml file.
Remember to replace bin/console by app/console if you are using
an older version of Symfony.
Tag
It will deploy to the last tag created or, if set, to a specific tag version. That is the only difference with the deploy options.
To deploy to last tag for the first host defined:
To deploy to version 1.4.1 for the first host defined:
Check the command reference to know all available
options. Options supplied to command take precedence over the ones
defined in the config.yml file.
Configuration reference
These are the default values, that may be overridden:
