πŸ“Š
Plesk

Managing Git Repositories in Plesk

πŸ“… 7 October 2026 ✏️ 7 October 2026 ⏱ 5 min leestijd

Learn how to create, manage, and automatically deploy Git repositories in Plesk, with practical steps and tips for secure workflows.

Plesk has built-in Git functionality that lets you create repositories directly from the panel and automatically deploy code to your website. You connect your local repository or a platform like GitHub via SSH, set up a webhook for automatic deployment, and manage everything clearly through the Plesk dashboard. Below you’ll find a step-by-step guide on how to set this up and which points you shouldn’t skip.

Creating a Git repository in Plesk

Log in to your Plesk management interface and go to the Websites & Domains section. Select the domain for which you want to create a repository and choose the ‘Git’ option. Click ‘Add Repository’ and choose whether to create a new (empty) repository or clone an existing one, for example from GitHub or GitLab.

Give the repository a clear name; this will become the folder where your project files end up. Plesk automatically generates a path and a repository URL that you use locally to push. First add your SSH key under your Plesk account settings, so you can connect securely without having to enter a password every time.

From your local machine, connect the repository as follows:

git remote add origin ssh://[email protected]/path/to/repo.gitngit push -u origin main
πŸ’‘ Tip: Always use SSH keys instead of passwords. This is more secure and prevents you from having to log in again with every push.

Automatic deployment with webhooks

With Git deployment in Plesk, you no longer have to upload files manually. As soon as you push to your repository, the new code is automatically copied to your live environment. This is especially useful if you work with a team or regularly roll out small updates.

LocalGit repoPlesk servergit pushwebhook

Go to the Git settings of your domain in Plesk and copy the webhook URL shown there. Add it to the webhook settings of your repository on GitHub or GitLab. From that moment on, every push will automatically trigger a new deployment.

1

Retrieve the webhook URL

Open the Git section of your domain in Plesk and copy the webhook URL listed there.

2

Register the webhook

Paste the URL into the webhook settings of your repository on GitHub, GitLab, or another platform.

3

Test the deployment

Push a small change and check whether it automatically appears on your server. If there are issues, check the deployment log in Plesk.

Managing and maintaining repositories

From the Plesk dashboard, you can view all your repositories per domain. Here you can delete repositories, re-clone them, and check the status of the latest deployment. It’s wise to regularly clean up old or unused repositories, so your environment stays organized.

Occasionally check the deployment logs in Plesk. Here you can see exactly which files were transferred and whether any errors occurred during the deployment process. This is the first place to look if an update didn’t come through correctly.

If you get stuck, you can find more background articles about Plesk management in the knowledge base, or you can contact 24/7 support via WhatsApp, ticket, or email.

Security and best practices

Make sure you use a properly configured .gitignore file, so sensitive files such as configuration files with passwords or API keys never end up in your repository. Always set repositories on platforms like GitHub or GitLab to ‘private’ unless there’s an explicit reason to make them public.

Limit SSH access to the keys you actually need and remove old keys as soon as team members are no longer active. Thanks to the daily backups of your hosting environment, your code remains protected even if something unexpectedly goes wrong during a deployment. If you don’t have hosting with these capabilities yet, check out the web hosting packages or read how switching to Tandata works.

Frequently Asked Questions

Can I create multiple repositories per domain in Plesk?

Yes. Each domain can have multiple repositories, each with its own path and independent management.

How do I secure my Git repository?

Use SSH keys instead of passwords, set your repository to private, and keep your .gitignore file up to date.

Does Git deployment work with every programming language?

Yes, the deployment feature in Plesk simply copies files. You can optionally add a build script that runs automatically after deployment.

What happens if a deployment fails?

Plesk shows an error message in the deployment log, so you can quickly see which step got stuck. Your previous, working version remains active in the meantime.

Are my repositories also included in the backups?

The files of your repository on the server fall under the regular daily backups of your hosting environment.

Conclusion

With Git in Plesk, you quickly set up a secure and organized deployment workflow: create a repository, connect an SSH key, set up a webhook, and your code is automatically rolled out. With regular maintenance and a good .gitignore file, you keep this process safe and manageable.

View web hosting β†’

Was dit artikel nuttig?