Plesk can deploy your website directly from a Git repository. This is useful for developers who want a clean “push/pull → deploy” workflow instead of uploading files manually.
What you need
- A Git repository (GitHub, GitLab, Bitbucket, or a private server).
- Access to your hosting in Plesk.
- If you use SSH to access the repository: an SSH key (Plesk can generate one).
Open Git in Plesk
- Log in to Plesk via My.GARMTECH.
- Go to Websites & Domains → Git.
If you do not see the Git option, it may be disabled for your plan. In this case, open a ticket from My.GARMTECH. (/tickets/create/step1)
Create a repository in Plesk
- Click Add Repository.
- Choose your repository type:
- Remote Git hosting — connect to an existing remote repository (recommended).
- Local repository on your workstation — Plesk creates an empty repo and gives you the URL to push to.
Choose a deployment method
Plesk supports multiple deployment workflows:
- Manual deployment: you pull changes and then click Deploy / Deploy from Repository in Plesk.
- Automatic deployment: Plesk deploys automatically after you pull changes (or after a webhook, depending on configuration).
- No deployment: repository is only stored, not published to the web root.
Recommended safe workflow (manual deploy)
- Push changes to your remote repository.
- In Plesk, open Websites & Domains → Git.
- Click Pull Updates (or similar option).
- Click Deploy from Repository.
- Test the website.
Notes for GARMTECH hosting
- Deployment directory: make sure Plesk deploys into the correct web root (commonly
httpdocs).
- Permissions: if the site shows 403/500 after deployment, check file permissions and the error log.
- Large frameworks: for Node.js builds or Composer installs, SSH access may be required (if available on your plan).
Related articles
- Enable SSH access for a hosting subscription in Plesk
- Upload website files in Plesk (httpdocs folder)
- View website logs in Plesk (error_log)