Automated Continuous Deployment to cPanel with Git & .cpanel.yml

Establishing an atomic, zero-downtime deployment pipeline to shared cPanel hosting directly from your local IDE terminal—eliminating manual FTP uploads and securing credentials.

Summary#

Shared cPanel hosting is frequently considered legacy infrastructure due to manual FTP uploads, lack of version control, and brittle configurations. By leveraging native Git repositories inside cPanel paired with .cpanel.yml deployment tasks, you can establish an automated, continuous deployment pipeline from your local terminal.

1. The Deployment Architecture#

Traditional FTP approaches suffer from three critical flaws:

1. No version rollback: Overwriting files in production leaves zero audit trail.
2. Partial uploads: Dropped network connections during FTP leave the site in an inconsistent, broken state.
3. Leaked credentials: FTP transmits credentials in plaintext or requires storing passwords in local clients.

The modern cPanel Git architecture resolves this by isolating the repository:

Local Workstation (Mac / Linux)
       │  git push origin main
       ▼
HostGator: /home/user/permesh-repo  (Bare or Isolated Git Repository)
       │  Triggered by post-receive / VersionControlDeployment
       ▼
HostGator: /home/user/public_html   (Clean production files only)

2. SSH Configuration & Port 2222#

HostGator and many shared hosts run SSH on Port 2222 instead of standard Port 22 to reduce automated brute-force attempts.

Configure your local ~/.ssh/config:

Host PerMesh
    HostName 216.172.172.88
    Port 2222
    User octola17
    IdentityFile ~/.ssh/id_rsa
    AddKeysToAgent yes
    UseKeychain yes

Test your SSH connection:

ssh -p 2222 octola17@permesh.com

3. Creating the Deployment Blueprint (.cpanel.yml)#

cPanel requires a file named .cpanel.yml in the root of your Git repository. It tells the cPanel deployment engine which files to copy into your web root (public_html):

---
deployment:
  tasks:
    - export DEPLOYPATH=/home1/octola17/public_html
    - /bin/cp -f index.php $DEPLOYPATH/ 2>/dev/null || true
    - /bin/cp -f .htaccess $DEPLOYPATH/ 2>/dev/null || true
    - /bin/cp -Rf assets $DEPLOYPATH/ 2>/dev/null || true
    - /bin/cp -Rf includes $DEPLOYPATH/ 2>/dev/null || true
    - /bin/cp -Rf pages $DEPLOYPATH/ 2>/dev/null || true

4. Key Takeaways#

• Security First: Keep .git and .env files completely outside public_html.
• Atomic Sync: .cpanel.yml copies updated files in milliseconds with zero downtime.
• Git as Source of Truth: Never edit live files via cPanel File Manager; push all changes through Git.