{"id":49777,"date":"2018-06-27T13:00:00","date_gmt":"2018-06-27T18:00:00","guid":{"rendered":"https:\/\/blog.cpanel.com\/?p=49777"},"modified":"2018-06-27T13:00:00","modified_gmt":"2018-06-27T18:00:00","slug":"git-version-control-soon-with-automatic-deployment","status":"publish","type":"post","link":"https:\/\/devel.www.cpanel.net\/blog\/products\/git-version-control-soon-with-automatic-deployment\/","title":{"rendered":"Git Version Control: Soon with Automatic Deployment!"},"content":{"rendered":"
This is the sixth and final blog post in a series around Git and a new feature in version 72,\u00a0Git Version Control<\/a>.\u00a0 See the full list of entries in this series at the end of this post!\u00a0This post talks about something that we’re adding in Version 74, which we expect will be entering EDGE sometime during the first week of July, and will be headed to CURRENT sometime in July!\u00a0<\/em><\/p>\n If you have been following along on the\u00a0feature request site<\/a>, you already know about our new feature, Git Version Control. We’re designing it to make hosting repositories as easy for developers as a “Hello World!” script\u00a0\u2014 and, in cPanel & WHM Version 74, we’re adding deployment to the mix, too!<\/p>\n This feature will let you create and manage repositories\u00a0and<\/strong>\u00a0view change history in a friendly interface.\u00a0A lot of Git’s functionality requires\u00a0command line<\/a>\u00a0knowledge<\/a>, but don’t worry! It’s easy to learn. Here’s the rundown on what you can expect from our new deployment functionality.<\/p>\n cPanel’s\u00a0Git Version Control<\/a><\/em>\u00a0feature (cPanel >> Home >> Files >> Git Version Control<\/em>) automatically adds a\u00a0 <\/a><\/p>\n Automatic or “push” deployment of a website<\/em>.<\/p>\n With automatic or push deployment, a single\u00a0 <\/a><\/p>\n Manual or “pull” deployment of a website with a remote repository<\/em>.<\/p>\n With manual or pull deployment, the\u00a0 Before deployment, repositories\u00a0must<\/strong>\u00a0meet the following requirements:<\/p>\n If a repository does\u00a0not<\/strong>\u00a0meet these requirements, the system will\u00a0not<\/strong>\u00a0display deployment information and will disable deployment functionality.<\/p>\n <\/a><\/p>\n If you already use Git, we hope that this\u00a0feature will knock your socks off! If you don’t, we’re hoping we can help you start!<\/p>\n A note fro<\/span>m benny: <\/span><\/em><\/p>\n Ready to give it a shot? The Git Version Control feature is already available to any server on the RELEASE tier. You can join us in our slack<\/a> or discord<\/a> channels, post your questions on the cPanel forums<\/a> or subreddit<\/a>, or come visit Houston, Texas for the 2018 cPanel Conference<\/a>, October 1st – 3rd. Need to catch up on the previous posts about Git Version control? Here they are!<\/em><\/p>\n This is the sixth and final blog post in a series around Git and a new feature in version 72,\u00a0Git Version Control.\u00a0 See the full list of entries in this series at the end of this post!\u00a0This post talks about something that we’re adding in Version 74, which we expect will be entering EDGE sometime […]<\/p>\n","protected":false},"author":77,"featured_media":64985,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[49],"tags":[653,2025,1869,2113,2089],"class_list":["post-49777","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-products","tag-git","tag-git-version-control","tag-v72","tag-v74","tag-version-control"],"acf":[],"yoast_head":"\n
\nAutomatic and Manual Deployment<\/h3>\n
post-receive<\/code>\u00a0hook to all cPanel-managed repositories.<\/p>\n
\n
.cpanel.yml<\/code>\u00a0file, the hook deploys those changes\u00a0automatically<\/strong>.<\/li>\n
git push<\/code>\u00a0command sends changes from your local computer to your cPanel-managed repository. The system then automatically runs the commands in your\u00a0
.cpanel.yml<\/code>\u00a0file to send changes from the cPanel-managed repository to a production directory. (For example, to the directory that contains your website’s public files.)<\/p>\n
git push<\/code>\u00a0command sends changes from your local computer to a remote repository. When you click\u00a0Update from Remote<\/em>\u00a0in the\u00a0Manage<\/em>\u00a0section of the\u00a0Git Version Control<\/a><\/em>\u00a0interface (cPanel >> Home >> Files >> Git Version Control<\/em>), the system retrieves changes from the remote repository and applies them to the cPanel-managed repository. When you click\u00a0Deploy HEAD Commit<\/em>, the system runs the commands in your\u00a0
.cpanel.yml<\/code>\u00a0file to send changes from the cPanel-managed repository to a production directory. (For example, to the directory that contains your website’s public files.) For a valid .cpanel.yml file, check our documentation site: Guide to Git: How to set up deployment<\/a><\/p>\n
Prerequisites<\/h3>\n
\n
.cpanel.yml<\/code>\u00a0file in the top-level directory.<\/li>\n
Awesome, right?<\/h3>\n
\n\n