{"id":633,"date":"2021-07-23T12:34:27","date_gmt":"2021-07-23T12:34:27","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/guide-to-git-how-to-set-up-deployment\/"},"modified":"2021-07-23T12:34:27","modified_gmt":"2021-07-23T12:34:27","slug":"guide-to-git-how-to-set-up-deployment","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/guide-to-git-how-to-set-up-deployment\/","title":{"rendered":"Guide to Git\u2122 – How to Set Up Deployment"},"content":{"rendered":"<\/p>\n
\n
<\/div>\n
\n

Overview<\/h2>\n

cPanel\u2019s Git Version Control<\/em> interface (cPanel >> Home >> Files >> Git Version Control<\/em>) allows you to configure deployment for your cPanel-managed repositories. While many deployment configurations are possible, this document only outlines two types of deployment that you can configure.<\/p>\n

Push<\/h3>\n

Push<\/strong> deployment first pulls changes from a remote repository to your local computer. Then, you can push them to your cPanel-managed repository. The system will automatically deploy changes that you push to the cPanel-managed repository.<\/p>\n<\/p>\n


\n
\nPush deployment.<\/em>
\n<\/center><\/p>\n

Pull<\/h3>\n

Pull<\/strong> deployment pulls changes from a remote repository to your local computer and pushes new changes from your local computer to the remote repository. You can then use the Git Version Control<\/em> interface (cPanel >> Home >> Files >> Git Version Control<\/em>) to manually deploy changes that you pull from the remote repository.<\/p>\n<\/p>\n

<\/p>\n
\n
\n<\/figure>\n

Pull deployment.<\/em>\n<\/p>\n

<\/center><\/p>\n

\n
Note:<\/div>\n
\n

If you experience issues when you configure Git deployment, read the following documents:<\/p>\n

    \n
  • \n

    Guide to Git – Set Up Access to Private Repositories<\/p>\n<\/li>\n

  • \n

    Git Version Control Series: Git Problems and How to Fix Them<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n

    Set up push deployment<\/h2>\n
    \n
    Note:<\/div>\n
    \n

    We recommend that you use this type of deployment.<\/p>\n<\/p><\/div>\n<\/div>\n

    Create an empty repository on your cPanel account.<\/h3>\n

    If the repository that you wish to deploy does not already exist on your cPanel account, use cPanel\u2019s Git Version Control<\/em> interface (cPanel >> Home >> Files >> Git Version Control<\/em>) to create one.<\/p>\n

    \n
    Note:<\/div>\n
    \n

    For this type of deployment, do not<\/strong> clone a remote repository during this step. Instead, create an empty repository.<\/p>\n<\/p><\/div>\n<\/div>\n

    Clone the remote repository to your local computer.<\/h3>\n

    If you have not already cloned it, clone the remote repository. For example, run the following command to clone a repository, where URL<\/code> represents the remote repository\u2019s clone URL:<\/p>\n

    \n
    git clone URL<\/code><\/pre>\n<\/div>\n
    \n
    Important:<\/div>\n
    \n
    To clone private repositories, you must perform additional steps. If you do not perform these steps, you will experience errors when you attempt to use Git. For more information, read our Guide to Git – Set Up Access to Private Repositories documentation.<\/p>\n<\/p><\/div>\n<\/div>\n
    \n
    Note:<\/div>\n
    \n
    You can find the repository\u2019s clone URL by performing the following steps:<\/p>\n
      \n
    1. \n
      Navigate to cPanel\u2019s Git Version Control<\/em> interface (cPanel >> Home >> Files >> Git Version Control<\/em>)<\/p>\n<\/li>\n
    2. \n
      Locate the desired repository in the list of repositories and click Manage<\/em>.<\/p>\n<\/li>\n
    3. \n
      The URL appears under the Clone URL<\/em> heading.<\/p>\n<\/li>\n<\/ol><\/div>\n<\/div>\n
      Create the .cpanel.yml file.<\/h3>\n
      In order to deploy changes from a cPanel-managed repository, you must<\/strong> check a .cpanel.yml<\/code> file in to the top-level directory of your repository. You can create and commit this file to your local computer\u2019s copy of the repository, or you can create and commit it on the remote repository.<\/p>\n
        \n
      • \n
        If you use the remote repository, you will require read-write access or can submit a pull request to the remote repository.<\/p>\n<\/li>\n
      • \n
        This tutorial uses changes from the local computer rather than the remote repository.<\/p>\n<\/li>\n<\/ul>\n
        For example, a .cpanel.yml<\/code> file may resemble the following example:<\/p>\n
        \n
        \n\n\n
        \n
        1\n<\/span>2\n<\/span>3\n<\/span>4\n<\/span>5\n<\/span>6\n<\/span><\/code><\/pre>\n<\/td>\n
        		\n
        ---\ndeployment:\n tasks:\n - export DEPLOYPATH=<\/span>\/home\/user\/public_html\/\n - \/bin\/cp index.html $DEPLOYPATH\n - \/bin\/cp style.css $DEPLOYPATH<\/code><\/pre>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<\/div>\n
        \n
        More:<\/div>\n
        \n
        For more information about the .cpanel.yml<\/code> file, read our Guide to Git – Deployment documentation.<\/p>\n<\/p><\/div>\n<\/div>\n
        Add the cPanel-managed repository as a remote.<\/h3>\n
        From your local computer, run the following command to add the cPanel-managed repository as the local computer\u2019s remote:<\/p>\n
        \n
        git remote add origin URL<\/code><\/pre>\n<\/div>\n
        In this command, URL<\/code> represents the cPanel-managed repository\u2019s clone URL.<\/p>\n
        Push changes to the cPanel-managed repository.<\/h3>\n
        From your local computer, run the following command to push the changes from your local computer to the cPanel-managed repository:<\/p>\n
        \n
        git push -u origin HEAD<\/code><\/pre>\n<\/div>\n
        After the cPanel-managed repository contains the .cpanel.yml<\/code> file, the system will automatically deploy any changes that you push to it.<\/p>\n
        \n
        Important:<\/div>\n
        \n
          \n
        • If you experience errors when you attempt to push your changes, the repository may be private and require SSH access. For more information, read our Guide to Git – Set Up Access to Private Repositories documentation.<\/li>\n<\/ul>\n
          Set up pull deployment<\/h2>\n
          Clone the remote repository to your cPanel account.<\/h3>\n
          If the repository that you wish to deploy does not already exist on your cPanel account, use cPanel\u2019s Git Version Control<\/em> interface (cPanel >> Home >> Files >> Git Version Control<\/em>) to clone the desired remote repository.<\/p>\n
          \n
          Note:<\/div>\n
          \n
          This feature enforces several restrictions on clone URLs, and it verifies the remote host\u2019s public SSH keys for ssh:\/\/<\/code> clone URLs.<\/p>\n<\/p><\/div>\n<\/div>\n
          Clone the remote repository to your local computer.<\/h3>\n
          If you have not<\/strong> already cloned the remote repository, use the terminal on your local computer to clone the remote repository.<\/p>\n
          For example, run the following command to clone a repository, where URL represents the remote repository\u2019s clone URL:<\/p>\n
          \n
          <p>git clone URL<\/p><\/code><\/pre>\n<\/div>\n
          Create the .cpanel.yml file.<\/h3>\n
          In order to deploy changes from a cPanel-managed repository, you must<\/strong> check a .cpanel.yml<\/code> file in to the top-level directory of your repository. You can create and commit this file to your local computer\u2019s copy of the repository, or you can create and commit it on the remote repository.<\/p>\n
          If you use the remote repository, you will require<\/strong> read-write access or can submit a pull request to the remote repository.
          \nThis tutorial uses changes from the local computer rather than the remote repository.<\/p>\n
          \n
          \n\n\n
          \n
          1\n<\/span>2\n<\/span>3\n<\/span>4\n<\/span>5\n<\/span>6\n<\/span><\/code><\/pre>\n<\/td>\n
          		\n
          ---\ndeployment:\n tasks:\n - export DEPLOYPATH=<\/span>\/home\/user\/public_html\/\n - \/bin\/cp index.html $DEPLOYPATH\n - \/bin\/cp style.css $DEPLOYPATH<\/code><\/pre>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<\/div>\n
          \n
          More:<\/div>\n
          \n
          For more information about the .cpanel.yml<\/code> file, read our Guide to Git – Deployment documentation.<\/p>\n<\/p><\/div>\n<\/div>\n
          Push changes to the remote repository.<\/h3>\n
          From your local computer, run the following command to push the changes from your local computer to the remote repository:<\/p>\n
          \n
          <p>git push origin HEAD<\/p><\/code><\/pre>\n<\/div>\n
          Pull and deploy changes from the cPanel interface.<\/h3>\n
          To pull the changes from the remote repository and then manually deploy them, perform the following steps:<\/p>\n
            \n
          1. \n
            Navigate to cPanel\u2019s Git Version Control<\/em> interface (cPanel >> Home >> Files >> Git Version Control<\/em>).<\/p>\n<\/li>\n
          2. \n
            Locate the desired repository in the list of repositories and click Manage<\/em>.<\/p>\n<\/li>\n
          3. \n
            Click the Pull or Deploy<\/em> tab.<\/p>\n<\/li>\n
          4. \n
            Click Update from Remote<\/em> to pull changes from the remote repository.<\/p>\n<\/li>\n
          5. \n
            Click Deploy HEAD Commit<\/em> to deploy your changes.<\/p>\n<\/li>\n<\/ol>\n
            Repeat these steps each time that you wish to pull and deploy changes. The system will not<\/strong> deploy changes for this deployment type automatically.<\/p>\n<\/p><\/div>\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"
            Overview cPanel\u2019s Git Version Control interface (cPanel >> Home >> Files >> Git Version Control) allows you to configure deployment for your cPanel-managed repositories. While many deployment configurations are possible, this document only outlines two types of deployment that you can configure. Push Push deployment first pulls changes from a remote repository to your local …<\/p>\n","protected":false},"author":1,"featured_media":634,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/633"}],"collection":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/comments?post=633"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/633\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/634"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=633"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=633"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=633"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}