Automatically deploy the code using PHP and Git.
git
andrsync
are required on the server that's running the script (server machine).- Optionally,
tar
is required for backup functionality (BACKUP_DIR
option). - Optionally,
composer
is required for composer functionality (USE_COMPOSER
option).
- Optionally,
- The system user running PHP (e.g.
www-data
) needs to have the necessary access permissions for theTMP_DIR
andTARGET_DIR
locations on the server machine. - If the Git repo you wish to deploy is private, the system user running PHP also needs to have the right SSH keys to access the remote repository.
- Configure the script and put it somewhere that's accessible from the
Internet. The prefered way to configure it is to use
deploy-config.php
file. Renamedeploy-config.example.php
todeploy-config.php
and edit the configuration options there. That way, you won't have to edit the configuration again if you download the new version ofdeploy.php
. - Configure your git repository to call this script when the code is updated. The instructions for GitHub and Bitbucket are below.
- (This step is only needed for private repositories) Go to
https://github.com/USERNAME/REPOSITORY/settings/keys
and add your server SSH key. - Go to
https://github.com/USERNAME/REPOSITORY/settings/hooks
. - Click Add webhook in the Webhooks panel.
- Enter the Payload URL for your deployment script e.g.
http://example.com/deploy.php?sat=YourSecretAccessTokenFromDeployFile
. - Optional Choose which events should trigger the deployment.
- Make sure that the Active checkbox is checked.
- Click Add webhook.
- (This step is only needed for private repositories) Go to
https://bitbucket.org/USERNAME/REPOSITORY/admin/deploy-keys
and add your server SSH key. - Go to
https://bitbucket.org/USERNAME/REPOSITORY/admin/services
. - Add POST service.
- Enter the URL to your deployment script e.g.
http://example.com/deploy.php?sat=YourSecretAccessTokenFromDeployFile
. - Click Save.
- Configure the SSH keys.
- Add a executable
.git/hooks/post_receive
script that calls the script e.g.
#!/bin/sh
echo "Triggering the code deployment ..."
wget -q -O /dev/null http://example.com/deploy.php?sat=YourSecretAccessTokenFromDeployFile
Next time you push the code to the repository that has a hook enabled, it's
going to trigger the deploy.php
script which is going to pull the changes and
update the code on the server machine.
For more info, read the source of deploy.php
.
- Because
rsync
is used for deployment, theTARGET_DIR
doesn't have to be on the same server that the script is running e.g.define('TARGET_DIR', 'username@example.com:/full/path/to/target_dir/');
is going to work as long as the user has the right SSH keys and access permissions. - You can have multiple scripts with different configurations. Simply rename
the
deploy.php
to something else, for exampledeploy_master.php
anddeploy_develop.php
and configure them separately. In that case, the configuration files need to be nameddeploy_master-config.php
anddeploy_develop-config.php
respectively.
Inspired by a Gist by oodavid