Plesk Git Setup

If your server is managed by Plesk, you can use Plesk's built-in Git deployment feature. EE Push triggers a Git pull via Plesk's REST API — no SSH configuration needed.

Prerequisites

Plesk with Git extension installed and enabled
A Git repository configured for your domain in Plesk
A Plesk API key with appropriate permissions
The curl PHP extension (usually installed by default)

Setting Up Plesk Git

Log into your Plesk panel
Go to your domain > Git
Add your repository URL and configure the deployment path
Set the branch to deploy
Generate an API key under Tools & Settings > API

Configuration in EE Push

Field	Description
Plesk API URL	Your Plesk server URL including port (e.g., `https://server.example.com:8443`). Required.
API Key	Plesk REST API key. Stored encrypted in the database.
Domain	The domain name as configured in Plesk (e.g., `example.com`).
Repository	The Git repository URL configured in Plesk (for reference only).

How It Works

When you deploy, EE Push sends a POST request to the Plesk REST API:

API request

POST https://server.example.com:8443/api/v2/domains/example.com/git/pull
Headers:
  Content-Type: application/json
  X-API-Key: [your-api-key]
Body:
  {"branch": "main"}

Plesk handles the Git pull, file deployment, and any configured post-deployment actions (like running Composer or clearing caches) on its end.

Generating a Plesk API Key

Go to Tools & Settings in Plesk
Click API (under Security)
Click Add Key
Give it a descriptive name (e.g., "EE Push Deploy")
Copy the key and paste it into the EE Push environment configuration

Security Notes

The API key is encrypted before being stored in the EE database
SSL certificate verification is handled by PHP's cURL
Consider restricting the API key's permissions to Git operations only