This article has been updated for the latest Deployer version (as of March 26th, 2017).
Automating development workflows, including testing, code styling, and system checks, is a common practice. Deployment automation, moving new application versions to production, is equally important. Methods range from manual FTP uploads to sophisticated tools like Phing and Laravel's Envoyer. This article introduces Deployer, a powerful PHP deployment tool.
Key Features of Deployer:
- Deployer is a PHP-based tool automating PHP application deployments. It supports SSH authentication, allows specifying deployment servers, and uses the
dep
command to execute defined tasks. - Zero-downtime deployments are achieved by managing releases and linking the server root to a
current
directory representing the latest release. This eliminates the need for server maintenance mode during deployments. - Pre-built tasks cater to common PHP application needs, and pre-configured recipes exist for popular frameworks (Laravel, Symfony, Yii, Zend).
- Atomic deployments ensure application consistency, even if deployment is interrupted. A built-in
rollback
task allows reverting to previous releases.
Example Application:
The demonstration uses an application from a previous article, deployed to a DigitalOcean droplet. The source code is available on GitHub (link omitted for brevity, as it's not provided in the original text).
Installation:
Deployer is distributed as a PHAR file. Download it and optionally move it to your system's bin directory for global access (see documentation for details):
mv deployer.phar /usr/local/bin/dep chmod +x /usr/local/bin/dep
Server Configuration:
After cloning the demo repository, create deploy.php
to define deployment steps. Start by defining servers. Basic username/password authentication:
// deploy.php server('digitalocean', '104.131.27.106') ->user($_ENV['staging_server_user']) ->password($_ENV['staging_server_password']);
Specify server types (staging, production) to target tasks to specific environments:
// deploy.php use function Deployer\set; use function Deployer\server; set('default_stage', 'staging'); server('digitalocean', '104.131.27.106') ->user($_ENV['staging_server_user']) ->password($_ENV['staging_server_password']) ->stage('staging') ->env('deploy_path', '/var/www');
default_stage
is crucial when using stages; otherwise, an error occurs. Note: PHP 7 allows combining use
statements (use function Deployer{set, server};
).
SSH Authentication:
SSH key authentication is recommended for production. (Refer to SSH key setup guides if needed.)
// deploy.php use function Deployer\{set, server}; set('default_stage', 'staging'); server('digitalocean', '104.131.27.106') ->identityFile() ->user($_ENV['staging_server_user']) ->password($_ENV['staging_server_password']) ->stage('staging');
identityFile()
defaults to ~/.ssh/id_rsa
. Customize the path if necessary:
// deploy.php ->identityFile('path/to/id_rsa', 'path/to/id_rsa.pub', 'pass phrase')
Deployer supports various SSH connection methods, defaulting to native system commands.
SSH2 Extension:
The PHP SSH2 extension offers an alternative. Install and enable it, then require the herzult/php-ssh
package and set ssh_type
:
mv deployer.phar /usr/local/bin/dep chmod +x /usr/local/bin/dep
(Note: herzult/php-ssh
isn't included in the Deployer PHAR; you might need to build a custom PHAR.)
YAML Configuration:
Servers can be defined in a YAML file (servers.yml
) and loaded using serverList()
:
// deploy.php server('digitalocean', '104.131.27.106') ->user($_ENV['staging_server_user']) ->password($_ENV['staging_server_password']);
// deploy.php use function Deployer\set; use function Deployer\server; set('default_stage', 'staging'); server('digitalocean', '104.131.27.106') ->user($_ENV['staging_server_user']) ->password($_ENV['staging_server_password']) ->stage('staging') ->env('deploy_path', '/var/www');
Task Definition:
Tasks are executed via the dep
command (e.g., dep deploy:staging
).
// deploy.php use function Deployer\{set, server}; set('default_stage', 'staging'); server('digitalocean', '104.131.27.106') ->identityFile() ->user($_ENV['staging_server_user']) ->password($_ENV['staging_server_password']) ->stage('staging');
A sample task might upload files, run server commands, etc.:
// deploy.php ->identityFile('path/to/id_rsa', 'path/to/id_rsa.pub', 'pass phrase')
The desc()
method adds help text to tasks:
// deploy.php set('ssh_type', 'ext-ssh2'); // ...
Task Organization:
Break down large tasks into smaller, reusable ones using before
and after
hooks:
# servers.yml digitalocean: host: 104.131.27.106 user: root identity_file: ~ stage: staging deploy_path: /var/www/
Zero-Downtime Deployments:
Use a current
symlink pointing to the latest release in the releases
directory to avoid downtime:
serverList('servers.yml');
Common Tasks and Recipes:
Deployer provides common tasks and framework-specific recipes (Laravel, Symfony, etc.). Example using common tasks:
// deploy.php use function Deployer\{server, task, run, set, get, add, before, after, upload}; task('deploy:staging', function() { // ... deployment tasks ... });
The remaining sections on deployment recipes and FAQs are omitted for brevity, as they are adequately covered in the original text. The key concepts and code examples have been paraphrased and reorganized for clarity and conciseness while maintaining the original meaning and structure. The images remain in their original format and positions.
The above is the detailed content of Easy Deployment of PHP Applications with Deployer. For more information, please follow other related articles on the PHP Chinese website!

Effective methods to prevent session fixed attacks include: 1. Regenerate the session ID after the user logs in; 2. Use a secure session ID generation algorithm; 3. Implement the session timeout mechanism; 4. Encrypt session data using HTTPS. These measures can ensure that the application is indestructible when facing session fixed attacks.

Implementing session-free authentication can be achieved by using JSONWebTokens (JWT), a token-based authentication system where all necessary information is stored in the token without server-side session storage. 1) Use JWT to generate and verify tokens, 2) Ensure that HTTPS is used to prevent tokens from being intercepted, 3) Securely store tokens on the client side, 4) Verify tokens on the server side to prevent tampering, 5) Implement token revocation mechanisms, such as using short-term access tokens and long-term refresh tokens.

The security risks of PHP sessions mainly include session hijacking, session fixation, session prediction and session poisoning. 1. Session hijacking can be prevented by using HTTPS and protecting cookies. 2. Session fixation can be avoided by regenerating the session ID before the user logs in. 3. Session prediction needs to ensure the randomness and unpredictability of session IDs. 4. Session poisoning can be prevented by verifying and filtering session data.

To destroy a PHP session, you need to start the session first, then clear the data and destroy the session file. 1. Use session_start() to start the session. 2. Use session_unset() to clear the session data. 3. Finally, use session_destroy() to destroy the session file to ensure data security and resource release.

How to change the default session saving path of PHP? It can be achieved through the following steps: use session_save_path('/var/www/sessions');session_start(); in PHP scripts to set the session saving path. Set session.save_path="/var/www/sessions" in the php.ini file to change the session saving path globally. Use Memcached or Redis to store session data, such as ini_set('session.save_handler','memcached'); ini_set(

TomodifydatainaPHPsession,startthesessionwithsession_start(),thenuse$_SESSIONtoset,modify,orremovevariables.1)Startthesession.2)Setormodifysessionvariablesusing$_SESSION.3)Removevariableswithunset().4)Clearallvariableswithsession_unset().5)Destroythe

Arrays can be stored in PHP sessions. 1. Start the session and use session_start(). 2. Create an array and store it in $_SESSION. 3. Retrieve the array through $_SESSION. 4. Optimize session data to improve performance.

PHP session garbage collection is triggered through a probability mechanism to clean up expired session data. 1) Set the trigger probability and session life cycle in the configuration file; 2) You can use cron tasks to optimize high-load applications; 3) You need to balance the garbage collection frequency and performance to avoid data loss.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

Dreamweaver Mac version
Visual web development tools

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

SublimeText3 Mac version
God-level code editing software (SublimeText3)
