Guide to Git™ – Deployment

Overview

The Git™ Version Control feature allows you to deploy your cPanel-managed repositories. Generally, deployment sends finished code into production. You can use different configurations to automatically (push deployment) or manually (pull deployment) deploy changes.

• For example, you could use deployment to make changes to your website locally. Then, automatically send them to a directory on your cPanel account.
• For more information about how to deploy changes, read our Git™ Version Control documentation.
• For more information about how to troubleshoot problems with this feature, read our Guide to Git – For System Administrators documentation.
• For more information about Git commands, such as git push, git pull, or git commit, read our Guide to Git™ – Common Git Commands documentation.

Requirements

Before deployment, repositories must meet the following requirements:

• A valid checked-in .cpanel.yml file in the top-level directory.
• One or more local or remote branches.
• A clean working tree.

If a repository does not meet these requirements, the system will not display deployment information. Also, it will disable deployment functionality.

The deployment YAML file

The .cpanel.yml file determines how and where the changed files deploy. You must check a .cpanel.yml file in to the top-level directory for each cPanel-managed repository that you deploy. The .cpanel.yml files must use the format in the examples below.

Deploy individual files

The following .cpanel.yml file deploys the index.html and style.css files to the example account’s public_html directory:

1
2
3
4
5
6

---
deployment:
  tasks:
    - export DEPLOYPATH=/home/user/public_html/
    - /bin/cp index.html $DEPLOYPATH
    - /bin/cp style.css $DEPLOYPATH

• Line 1 is the beginning of a YAML file.
• Lines 2 and 3 add the deployment and tasks keys, respectively.
• Lines 4 through 6 specify an array of BASH commands to run during deployment. You can add as many commands to this array as you wish.

Deploy an entire directory

The following .cpanel.yml file copies the images directory and all of its contents to the example account’s public_html directory:

1
2
3
4
5

---
deployment:
  tasks:
    - export DEPLOYPATH=/home/example/public_html/
    - /bin/cp -R images $DEPLOYPATH

• Line 1 is the beginning of a YAML file.
• Lines 2 and 3 add the deployment and tasks keys, respectively.
• Lines 4 and 5 specify an array of BASH commands to run during deployment. You can add as many commands to this array as you wish.

Automatic or push deployment

With push deployment, a single git push command sends changes from your local computer to your cPanel-managed repository. The system then automatically runs the commands in your .cpanel.yml file. This configuration will send changes from the cPanel-managed repository to a production directory. (For example, to the directory that contains your website’s public files.)

Manual or pull deployment

With pull deployment, the git push command sends changes from your local computer to a remote repository.

• When you click Update from Remote in the Pull or Deploy tab of the Manage section of cPanel’s Git™ Version Control interface (cPanel >> Home >> Files >> Git Version Control), the system retrieves changes from the remote repository and applies them to the cPanel-managed repository.

• When you click Deploy HEAD Commit, the system runs the commands in your .cpanel.yml file to send changes from the cPanel-managed repository to a production directory. (For example, to the directory that contains your website’s public files.)