In this book, we will take a tour of the version control system GitLab, which is based on Git. It's open source and has many great features that we will learn chapter wise as listed here. First, we will take a look at what GitLab can do for us, and later we will see how we can install it on a server and configure it to match our needs.
The next step is to take a close look at the web interface, and then we will learn how to handle permissions and teams, document our code, track issues, and show example workflows.
Lastly, we will learn how to perform maintenance for our installation, including the creation of backups and upgrading to the most recent version. We will also cover getting in touch with the community and developers on the respective channels.
Chapter 1, Kickstarting with GitLab, covers a short introduction of GitLab, its key features, and origin of the project.
Chapter 2, Installation, covers the preparation of the environment and installation of the dependencies and GitLab itself on a Linux box.
Chapter 3, Configuring GitLab, explains the setting up of GitLab's configuration and making it match our needs in terms of security; we will also learn what setting can be changed from where.
Chapter 4, Roles and Permissions, covers exploring of the web interface. We will also learn how to use roles inside GitLab to distribute power, access restrictions, and set up teams that work nicely.
Chapter 5, Issues and Wikis, covers the documentation of software and its development through built-in wikis. Use of issue tracking inside GitLab and assigning issues to developers will also be covered in this chapter.
Chapter 6, Workflows, explores the different styles of working with Git and GitLab. We will also learn how to find the right workflow and see how GitLab supports this.
Chapter 7, Updating GitLab, covers the creation of backups, stop services, and updates for the latest version. We will also run tests to see if everything is up to speed.
Chapter 8, Help and Community, covers the connection with the community and developers. We will also come to know the different channels and where we can submit feature requests or make contributions to the project.
We will need either a computer or virtual machine that is running Debian or Debian derivative Linux, such as Ubuntu. Furthermore, we'll need an Internet connection for the download of the required software.
Do you want to drive Git to its full potential? Do you want to involve your team members at different skill levels, take work off your day-to-day workflow with Git, and migrate to it with an approachable interface? That's what you can do with GitLab, and this book is for you then!
Also, if you want to gain experience with one of the best possibilities of creating a server's IDE infrastructure for code version control, this comprehensive guide will provide steps to follow and possibilities to explore.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Some examples of these styles are given here with an explanation of their meaning.
Code words in text are shown as follows: "The great thing about Git is that it will install all versions at once, and you can choose between them at any time by running the checkout command for the version compatible to GitLab 5.0."
A block of code is set as follows:
git remote add origin ssh://user@host:3101/git/example
Any command-line input or output is written as follows:
cd /home/git/gitlab sudo gem install charlock_holmes --version '0.6.9.4'
New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "By navigating to the Issues tab of a repository in the web interface, you can easily create new issues."
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply send an e-mail to <[email protected]>, and mention the book title via the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
You can download the example code files for all Packt books you have purchased from your account at http://www.packtpub.com. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors, and our ability to bring you valuable content.
You can contact us at <[email protected]> if you are having a problem with any aspect of the book, and we will do our best to address it.