Skip to content
  • Solutions
    By Role
    • For Developers
    • For Content Managers
    • For Agencies
    • For IT Admins
    • For Web Hosters
    • For Developers
    • For Content Managers
    • For Agencies
    • For IT Admins
    • For Web Hosters
    By Infrastructure
    • Overview
    • AWS
    • Microsoft Azure
    • Alibaba Cloud
    • Google Cloud Platform
    • Vultr
    • Overview
    • AWS
    • Microsoft Azure
    • Alibaba Cloud
    • Google Cloud Platform
    • Vultr
    • Digital Ocean
    • Linode
    • Upcloud
    • Oracle
    • OVH
    • Digital Ocean
    • Linode
    • Upcloud
    • Oracle
    • OVH
  • Product
    • Plesk Features
    • Plesk Editions
    • What’s new
    • Pricing
    • Roadmap
    • Lifecycle Policy
    • Extensions Catalogue
  • Pricing
  • Extensions
    Featured Extensions
    • SocialBee
    • WP Toolkit
    • Sitejet Builder for Plesk
    • SEO Toolkit
    • Joomla! Toolkit
    • Premium Email
    • Email Security
    • SocialBee
    • WP Toolkit
    • Sitejet Builder for Plesk
    • SEO Toolkit
    • Joomla! Toolkit
    • Premium Email
    • Email Security
    Bundles and packs:
    • Business and Collaboration Edition
    • WP pack
    • Hosting pack
    • Power pack
    • Language pack
    • Business and Collaboration Edition
    • WP pack
    • Hosting pack
    • Power pack
    • Language pack

    See all Extensions

  • For Partners
    • Plesk Contributor Program
    • Plesk Partner Program
    • Affiliate program
    • Plesk University
  • Help Center
    • Documentation
    • Professional Services
    • Support
    • Contact Us
    • Wiki
    • Forum
  • Plesk 360 login
  • Free Trial
  • Pricing
  • Solutions
    • By Role
      • For Developers
      • For Content Managers
      • For Agencies
      • For IT Admins
      • For Web Hosters
    • By Infrastructure
      • Overview
      • Plesk on Amazon Web Services (AWS & Lightsail)
      • Microsoft Azure
      • Alibaba Cloud
      • Google Cloud Platform
      • Vultr
      • DigitalOcean
      • Linode
      • UpCloud
      • Oracle
      • OVH
  • Products
  • Pricing
  • Extensions
    • Featured Extensions
      • SocialBee
      • WP Toolkit
      • Sitejet Builder for Plesk
      • SEO Toolkit
      • Joomla! Toolkit
      • Premium Email
      • Email Security
    • Bundles and packs:
      • Business and Collaboration Edition
      • WP pack
      • Hosting pack
      • Power pack
      • Language pack
      • See all Extensions
  • For Partners
    • Plesk Contributor Program
    • Plesk Partner Program
    • Affiliate Program
    • Plesk University
  • Help Center
    • Documentation
    • Professional Services
    • Support
    • Contact Us
    • Wiki
    • Forum
  • Plesk 360 login
  • Free Trial
  • Pricing
  • Solutions
    • By Role
      • For Developers
      • For Content Managers
      • For Agencies
      • For IT Admins
      • For Web Hosters
    • By Infrastructure
      • Overview
      • Plesk on Amazon Web Services (AWS & Lightsail)
      • Microsoft Azure
      • Alibaba Cloud
      • Google Cloud Platform
      • Vultr
      • DigitalOcean
      • Linode
      • UpCloud
      • Oracle
      • OVH
  • Products
  • Pricing
  • Extensions
    • Featured Extensions
      • SocialBee
      • WP Toolkit
      • Sitejet Builder for Plesk
      • SEO Toolkit
      • Joomla! Toolkit
      • Premium Email
      • Email Security
    • Bundles and packs:
      • Business and Collaboration Edition
      • WP pack
      • Hosting pack
      • Power pack
      • Language pack
      • See all Extensions
  • For Partners
    • Plesk Contributor Program
    • Plesk Partner Program
    • Affiliate Program
    • Plesk University
  • Help Center
    • Documentation
    • Professional Services
    • Support
    • Contact Us
    • Wiki
    • Forum
  • Plesk 360 login
  • Free Trial
Plesk 360 login
Free Trial

Knowledge Base

Using remote Git hosting – Clone Git Repository

 
customer guidegit supportusing remote git hostingcloningdeployment

You can create a Git repository that will be a clone of a remote
repository. Go to Websites&Domains and click Git. If you have
already created Git repositories for your domain, click the Add
Repository
button. You will see the screen for creating a new
repository:

image 76919

First, you have to select where your code is stored. In this scenario,
select Remote git hosting like GitHub or BitBucket.

Remote Git repository. Enter the path to your remote repository in
BitBucket or GitHub. You can enter it in either HTTPS or SSH format.
HTTP/HTTPS authentication is not supported, so you can use HTTP/HTTPS
protocol only if a repository does not require authentication. If a
private Git repository is used, you must authenticate with an SSH key
generated by Plesk (refer to Use SSH Connection
for details).

In the Your Website section, specify the following:

  • The deployment mode. By default, the Automatic deployment is
    used. This means that all changes pushed to the Git repository will
    be automatically deployed to the production site. If you want to
    change the deployment mode, click the automatically deployed link
    and select another option in the opened Deployment Mode window.
    If Manual deployment is selected, you will need to manually
    deploy files from the Git repository to your hosting. If No
    deployment
    is selected, the files will not be deployed to the
    production site (this can be used, for example, to store and exchange
    code).

    image 76254

  • A target directory for publishing Git files on your website. By
    default, the /httpdocs directory is used. You can change it to
    another existing directory by clicking the directory name.

    image 76255

Click OK. Plesk will try to connect to the remote repository and
clone it.

image 76455

After the progress dialog shows that the cloning has completed
successfully, the new repository will be displayed on the Git page.

image 76456

The new repository will be displayed at Websites & Domains >
Git. The name of the remote repository will be used as a Git
repository name. You can rename the repository later (refer to the
Rename or Remove a Repository section).

The created repository is a clone of the remote repository and will be
used for pulling changes from it and deploying them to the target
directory.

image 76920

Tweet
Share
Share
Email
0 Shares
Read the full article
Related Posts

The DevOps Cycle 2: Automated Deployment, Operations and Monitoring

Read More »

Plesk on DigitalOcean is now a one-click app

Read More »

Deploying Plesk Onyx on Microsoft Windows Azure

Read More »
Knowledge Base

Using remote Git hosting – Use Webhooks for Automatic Pull

Read More »

Using remote Git hosting

Read More »

Using remote Git hosting – Using SSH Connection

Read More »

Using remote Git hosting – Enable Additional Deployment Actions

Read More »

Hosting Wiki

  • GIT
  • GitHub
  • HTTP/3
  • HTTP/2
  • Domain
  • Hosting Control Panel
  • Lighttpd
  • SSH
  • Colocation Hosting
  • Reseller Hosting
  • Cloud Hosting
  • VPS Hosting
  • Dedicated Hosting
  • Shared Hosting
  • Free Hosting
  • Managed Hosting
  • HTTP
X-twitter Linkedin Youtube Reddit Github
  • Product
  • Login
  • Pricing
  • Editions
  • For Partners
  • Partner Program
  • Contributor Program
  • Affiliate Program
  • Plesk University
  • Company
  • Blog
  • Careers
  • Events
  • About Plesk
  • Our Brand
  • Resources
  • User and Admin guides
  • Help Center
  • Migrate to Plesk
  • Contact Us
  • Hosting Wiki
  • Forum
  • Legal
  • Legal
  • Privacy Policy
  • Imprint

© 2025 WebPros International GmbH

Part of the WebPros®  Family