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

Overview<\/h2>\n

The Git\u2122 Version Control<\/em> feature allows you to deploy your cPanel-managed repositories. Generally, deployment sends finished code into production. You can use different configurations to automatically (push deployment) or manually (pull deployment) deploy changes.<\/p>\n

    \n
  • For example, you could use deployment to make changes to your website locally. Then, automatically send them to a directory on your cPanel account.<\/li>\n
  • For more information about how to deploy changes, read our Git\u2122 Version Control<\/em> documentation.<\/li>\n
  • For more information about how to troubleshoot problems with this feature, read our Guide to Git – For System Administrators documentation.<\/li>\n
  • For more information about Git commands, such as git push<\/code>, git pull<\/code>, or git commit<\/code>, read our Guide to Git\u2122 – Common Git Commands documentation.<\/li>\n<\/ul>\n

    Requirements<\/h2>\n

    Before deployment, repositories must<\/strong> meet the following requirements:<\/p>\n

      \n
    • A valid checked-in .cpanel.yml<\/code> file in the top-level directory.<\/li>\n
    • One or more local or remote branches.<\/li>\n
    • A clean working tree.<\/li>\n<\/ul>\n

      If a repository does not<\/strong> meet these requirements, the system will not<\/strong> display deployment information. Also, it will disable deployment functionality.<\/p>\n

      The deployment YAML file<\/h2>\n

      The .cpanel.yml<\/code> file determines how and where the changed files deploy. You must check a .cpanel.yml<\/code> file in to the top-level directory for each cPanel-managed repository that you deploy. The .cpanel.yml<\/code> files must use the format in the examples below.<\/p>\n

      \n
      Important:<\/div>\n
      \n
        \n
      • The files below are only examples<\/strong>. You must<\/strong> update them to suit your needs. These files will not allow you to deploy a repository successfully.<\/li>\n
      • Don\u2019t<\/strong> use a wildcard character, such as an asterisk, to deploy all files. This could deploy items like the .git<\/code> directory and cause serious problems.<\/li>\n
      • Don\u2019t<\/strong> use characters that are invalid in YAML files. For more information, read the Escaped Characters section of yaml.org\u2019s YAML Specification.<\/li>\n<\/ul><\/div>\n<\/div>\n

        Deploy individual files<\/h3>\n

        The following .cpanel.yml<\/code> file deploys the index.html<\/code> and style.css<\/code> files to the example<\/code> account\u2019s public_html<\/code> directory:<\/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
        ---<\/span>\ndeployment:\n  tasks:\n    -<\/span> export DEPLOYPATH=<\/span>\/home\/<\/span>user\/public_html\/<\/span>\n    -<\/span> \/bin\/c<\/span>p index.<\/span>html $DEPLOYPATH\n    -<\/span> \/bin\/c<\/span>p style.<\/span>css $DEPLOYPATH<\/code><\/pre>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<\/div>\n
          \n
        • Line 1 is the beginning of a YAML file.<\/li>\n
        • Lines 2 and 3 add the deployment<\/code> and tasks<\/code> keys, respectively.<\/li>\n
        • Lines 4 through 6 specify an array of BASH commands to run during deployment. You can add as many commands to this array as you wish.<\/li>\n<\/ul>\n
          \n
          Note:<\/div>\n
          \n
          To add comments to this file, add a line that begins with the hash character (#<\/code>).<\/p>\n<\/p><\/div>\n<\/div>\n
          Deploy an entire directory<\/h3>\n
          The following .cpanel.yml<\/code> file copies the images<\/code> directory and all of its contents to the example<\/code> account\u2019s public_html<\/code> directory:\n<\/p>\n
          \n
          \n\n\n
          \n
          1\n<\/span>2\n<\/span>3\n<\/span>4\n<\/span>5\n<\/span><\/code><\/pre>\n<\/td>\n
          		\n
          ---<\/span>\ndeployment:\n  tasks:\n    -<\/span> export DEPLOYPATH=<\/span>\/home\/<\/span>example\/public_html\/<\/span>\n    -<\/span> \/bin\/c<\/span>p -<\/span>R images $DEPLOYPATH<\/code><\/pre>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<\/div>\n
            \n
          • Line 1 is the beginning of a YAML file.<\/li>\n
          • Lines 2 and 3 add the deployment<\/code> and tasks<\/code> keys, respectively.<\/li>\n
          • Lines 4 and 5 specify an array of BASH commands to run during deployment. You can add as many commands to this array as you wish.<\/li>\n<\/ul>\n
            \n
            Note:<\/div>\n
            \n
            To add comments to this file, add a line that begins with the hash character (#<\/code>).<\/p>\n<\/p><\/div>\n<\/div>\n
            Automatic or push deployment<\/h2>\n
            \n
            Important:<\/div>\n
            \n
            cPanel\u2019s Git\u2122 Version Control<\/em> interface (cPanel >> Home >> Files >> Git Version Control<\/em>) automatically adds a post-receive hook to all cPanel-managed repositories.<\/p>\n
              \n
            • When you push changes directly to a cPanel-managed repository that includes a .cpanel.yml<\/code> file, the hook deploys those changes automatically.<\/li>\n
            • For more information, read Git\u2019s githooks documentation.<\/li>\n<\/ul><\/div>\n<\/div>\n
              <\/p>\n
              \n    
              \n<\/figure>\n<\/p>\n
              <\/center><\/p>\n
              With push deployment, a single git push<\/code> command sends changes from your local computer to your cPanel-managed repository. The system then automatically runs the commands in your .cpanel.yml<\/code> file. This configuration will send changes from the cPanel-managed repository to a production directory. (For example, to the directory that contains your website\u2019s public files.)<\/p>\n
              \n
              Note:<\/div>\n
              \n
              You can use manual deployment to deploy your repository again without new changes.<\/p>\n<\/p><\/div>\n<\/div>\n
              Manual or pull deployment<\/h2>\n<\/p>\n
              <\/p>\n
              \n    
              \n<\/figure>\n<\/p>\n
              <\/center><\/p>\n
              With pull deployment, the git push<\/code> command sends changes from your local computer to a remote repository.<\/p>\n
                \n
              • \n
                When you click Update from Remote<\/em> in the Pull or Deploy<\/em> tab of the Manage<\/em> section of cPanel\u2019s Git\u2122 Version Control<\/em> interface (cPanel >> Home >> Files >> Git Version Control<\/em>), the system retrieves changes from the remote repository and applies them to the cPanel-managed repository.<\/p>\n<\/li>\n
              • \n
                When you click Deploy HEAD Commit<\/em>, the system runs the commands in your .cpanel.yml<\/code> file to send changes from the cPanel-managed repository to a production directory. (For example, to the directory that contains your website\u2019s public files.)<\/p>\n<\/li>\n<\/ul><\/div>\n","protected":false},"excerpt":{"rendered":"
                Overview The Git\u2122 Version Control feature allows you to deploy your cPanel-managed repositories. Generally, deployment sends finished code into production. You can use different configurations to automatically (push deployment) or manually (pull deployment) deploy changes. For example, you could use deployment to make changes to your website locally. Then, automatically send them to a directory …<\/p>\n","protected":false},"author":1,"featured_media":624,"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\/623"}],"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=623"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/623\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/624"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=623"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=623"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=623"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}