Barry Rowlingson CHICAS use of git lab
Download as PPTX, PDF•1 like•1,107 views
This document discusses using GitLab for revision control and managing code. It notes some common barriers to using Git like not wanting to share code or feeling code is not ready to share. It then compares GitLab to GitHub and discusses how to set up a GitLab instance on campus for private code repositories with total privacy and control. Installation of GitLab was described as easy and it provides benefits like backups of work and adding collaborators.
Barry Rowlingson CHICAS use of git lab
- 1. CHICAS’ Use of GitLab - some notes Lancaster University Data Conversations 3rd October 2017 Barry Rowlingson
- 2. Revision Control ●Is a good thing ●Git is a really good thing ●Barriers to using Git?
- 3. Barriers to Using Git “I don’t want to share my code” ○You don’t have to, have a local repository. “I can’t share my code with everyone” ○You don’t have to, have a private repository. “My code is rubbish, nobody should see it” ○Everyone’s code is, together we can make it better. “My code is valuable, I don’t want it off-site” ○So self-host a git repository.
- 4. GitHub.com ●Limited free private repos. ●Can’t be self- hosted.
- 5. GitLab.com ●Similar feature-set. ●Limited free private repos. ●Open source. ●Can be self- hosted.
- 6. fhm-chicas-code.lancs.ac.uk ●Get an ISS VM ●Install GitLab
- 7. Minuses ●Installation ○“Omnibus” installation on Ubuntu was easy. ●Admin ○Add users. ●Maintenance ○Look out for security updates ○Look out for update messages ○Run “apt-get install gitlab-ce” occasionally.
- 8. Pluses ●Personal Git Repositories ○Single user, backups your working directory ●Total Privacy ○Nothing leaves campus ●Total Control ○We can easily add outside collaborators
- 9. Private-public FrankD pushed a project from our GitLab to GitHub for public consumption.
- 10. Conclusion ●Use Gitlab ●Go on ●Go on ●Go on ●Go on….