Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering GitLab 12

You're reading from   Mastering GitLab 12 Implement DevOps culture and repository management solutions

Arrow left icon
Product type Paperback
Published in Aug 2019
Publisher Packt
ISBN-13 9781789531282
Length 608 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Joost Evertse Joost Evertse
Author Profile Icon Joost Evertse
Joost Evertse
Arrow right icon
View More author details
Toc

Table of Contents (30) Chapters Close

Preface 1. Section 1: Install and Set Up GitLab On-Premises or in the Cloud FREE CHAPTER
2. Introducing the GitLab Architecture 3. Installing GitLab 4. Configuring GitLab Using the Web UI 5. Configuring GitLab from the Terminal 6. Section 2: Migrating Data from Different Locations
7. Importing Your Project from GitHub to GitLab 8. Migrating from CVS 9. Switching from SVN 10. Moving Repositories from TFS 11. Section 3: Implement the GitLab DevOps Workflow
12. GitLab Vision - the Whole Toolchain in One Application 13. Create Your Product, Verify, and Package it 14. The Release and Configure Phase 15. Monitoring with Prometheus 16. Integrating GitLab with CI/CD Tools 17. Section 4: Utilize GitLab CI and CI Runners
18. Setting Up Your Project for GitLab Continuous Integration 19. Installing and Configuring GitLab Runners 20. Using GitLab Runners with Docker or Kubernetes 21. Autoscaling GitLab CI Runners 22. Monitoring CI Metrics 23. Section 5: Scale the Server Infrastructure (High Availability Setup)
24. Creating a Basic HA Architecture Using Horizontal Scaling 25. Managing a Hybrid HA Environment 26. Making Your Environment Fully Distributed 27. Using Geo to Create Distributed Read-Only Copies of GitLab 28. Assessments 29. Other Books You May Enjoy

The difference between SVN and Git

Like CVS, the biggest difference between Git and SVN is that SVN follows a centralized architecture, while Git uses a distributed network. There is one SVN server, and as a client you communicate your changes with it. This in different to Git, where there can be many local copies, and one copy can reside on a central server. This architecture is depicted as follows:

With Git, there are several options to choose from regarding protocol and network settings. Most importantly, you have the choice to communicate with remotes over SSH or HTTP. Using SSH, you wrap Git commands, possibly using certificate authentication, and with HTTP, you implement Git actions using WebDAV and basic HTTP authentication.

SVN has a networking layer that is abstracted, which means that clients exhibit the same behavior, no matter what sort of server they are operating...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime