Why Deployer? Provision Deployer will configure your server, setup a firewall, install PHP and MySQL or Postgres, configure HTTPS, etc.

Deployer will prompt you with a series of questions. After completing them, you'll have a deploy.php or * deploy.yaml * file—your deployment recipe. This file defines hosts, tasks, and …

There are two ways to install Deployer: globally or locally. Global installation is recommended for most users, as it allows you to use Deployer from any directory.

By now, you should have a solid understanding of Deployer’s basics, from defining tasks and hosts to working with configurations and dynamic values. Happy deploying!

This is documentation for Deployer 6.x, which is no longer actively maintained. For up-to-date documentation, see the latest version (8.x).

This is documentation for Deployer 6.x, which is no longer actively maintained. For up-to-date documentation, see the latest version (8.x).

This is documentation for Deployer 7.x, which is no longer actively maintained. For up-to-date documentation, see the latest version (8.x).

Deployer will ask you a few questions during provisioning: php version, database type, etc. Next, Deployer will configure our server and create the deployer user.

Deployer uses the selector to choose hosts. Next, it takes the given task, performs some preparation (described later), and executes the task on all selected hosts.

Deployer will now connect using ssh [email protected]. Alternatively, you can use special setter methods for better IDE autocompletion: