Environments
Environments are the core building blocks of EE Push. Each environment represents a deployment target — a server or service that receives your code changes.
What Are Environments?
- Development — Your local or shared dev server where features are built and tested.
- Staging — A pre-production environment that mirrors production for final QA.
- Production — The live site. Deployments here should be carefully tested and optionally approved.
Creating an Environment
- Navigate to Add-Ons > EE Push > Environments
- Click Create Environment
- Fill in the fields and click Save
Environment Fields
| Field | Description |
|---|---|
| Name | A descriptive label (e.g., "Production", "Staging"). |
| Type | Deployment method: webhook, ssh, or plesk. |
| Branch | Git branch to deploy (e.g., main, develop). |
| DB Mode | How the database is handled. See Database Modes. |
| Is Staging | Enables Full DB Replace. Blocked for non-staging environments. |
| Health Check URL | URL to verify after deployment (expects HTTP 200). |
| Exclude Patterns | Files/directories to exclude. One per line. |
| Sort Order | Controls display order (lower = first). |
Exclude Patterns Example
Example exclude patterns
cache/*
uploads/*
.env
system/user/config/config.phpType-Specific Configuration
Each type shows additional fields. See the setup guides:
- Webhook Setup — URL, headers, HMAC secret
- SSH Setup — Host, credentials, remote path, commands
- Plesk Setup — API URL, API key, domain
Editing & Deleting
Click an environment name to edit. Changes take effect immediately. To delete, click Delete — environments with active deployments cannot be deleted. Deployment history is retained in the logs.
Encrypted Credentials
All sensitive credentials are encrypted via EE's Encrypt service before storage. They are decrypted only during deployment execution and never shown after the initial save.