Download as PDF, PPTX
![3. Git Hooks
● 2 types: client and server hooks
● Client:
○ pre/post-commit
○ [prepare-]commit-msg
○ post-checkout, post-merge
● Server:
○ pre/post-receive Once per push
○ update Once per pushed branch
http://git-scm.com/book/en/Customizing-Git-Git-Hooks](https://image.slidesharecdn.com/gitdeployment-130614134654-phpapp02/85/Deployment-made-easy-with-Git-8-320.jpg)
Uploaded byIgor Santos
Deployment made easy with Git
The document provides a tutorial on deploying code using Git, focusing on basic commands such as commit, pull, and push, as well as configuring a server for deployment. It introduces Git hooks for automating tasks during the commit and push processes, and demonstrates how to set up a deployment script. Additionally, it discusses advanced deployment options, including services like DeployHQ that facilitate code deployment through various methods.
More Related Content
Similar to Deployment made easy with Git
Deployment made easy with Git
- 1.
- 2. Igor Santos Web developer ●From Rio de Janeiro, Brazil ● PHP Developer for ~6 years ● Ruby and JS Developer for fun ● Playing around with git for ~2 years slideshare.net/igorsantos07
- 3. 0. Introduction ● Knowswhat Git is? ● Have ever used Git in the command line? ● Have ever deployed code? ○ How? SCP? WGet? ● Anyone developing in the production server?
- 4. 1. Git Basics ●Commit: Saves changes with a description ● Pull: Get commits from a server ● Push: Send commits to a server ● Remotes ○ A remote machine that has a copy of the repository and accepts your commits ○ In a common centralized organization you usually have one, but it's possible to have many ○ Example: main repo is BitBucket or Google Code, mirrored to GitHub
- 5. 2. Configure yourserver igor@local$ ssh santos@bluenose.cs.dal.ca password: ********** santos@bluenose$ mkdir repos santos@bluenose$ cd repos santos@bluenose$ pwd /users/cs/santos/repos santos@bluenose$ git clone «repo» myRep --bare This creates a clone of that repository that works just as another repository: with all administrative data, but not useable for development, as the code is not really checked in - just the Git meta-data. Take note
- 6. igor@local$ cd dev/myCode igor@local$git remote add prod ssh://santos@bluenose.cs.dal.ca:/users/cs/santos/repos/myRep igor@local$ "Hi there!" > README.mkd igor@local$ git commit "+ Adding readme" igor@local$ git push prod 2. Configure your server Name given to the remote server Complete repository URL No line break!
- 7. igor@local$ git commit"+ Adding readme" igor@local$ git push prod Q: OK, so... where's my README file? A: In the repository! Q: I can't see it. «not really a question» 2. Configure your server
- 8. 3. Git Hooks ●2 types: client and server hooks ● Client: ○ pre/post-commit ○ [prepare-]commit-msg ○ post-checkout, post-merge ● Server: ○ pre/post-receive Once per push ○ update Once per pushed branch http://git-scm.com/book/en/Customizing-Git-Git-Hooks
- 9. 3. Git Hooks Simplecopy $ cat hooks/post-receive #!/bin/sh GIT_WORK_TREE=/var/www/mysite git checkout -f Opposite of git clone --bare: copies the entire repository code, without git data. By default does that with the master branch, but you can use other options here as well. GIT_WORK_TREE tells git where it would copy stuff.
- 10. 3. Git Hooks Completedeployment script https://bitbucket.org/igorsantos07/calen-do/src/3fea92ee46c1/git-hooks/update
- 11. 4. Advanced ideas GitHuband other Git online repositories have options to do HTTP requests with code information after pushes, similar to post- receive hooks. This data can be used to trigger a deployment script in the server. There's also an online service called DeployHQ, where you can configure any repository (SVN/Git/Hg) and many deploy methods (FTP/SFTP/S3/Rackspace). It deploys new code using the chosen method.
- 12.