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
Gitlab Cookbook

You're reading from   Gitlab Cookbook Over 60 hands-on recipes to efficiently self-host your own Git repository using GitLab

Arrow left icon
Product type Paperback
Published in Dec 2014
Publisher
ISBN-13 9781783986842
Length 172 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Jeroen van Baarsen Jeroen van Baarsen
Author Profile Icon Jeroen van Baarsen
Jeroen van Baarsen
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. Introduction and Installation 2. Explaining Git FREE CHAPTER 3. Managing Users, Groups, and Permissions 4. Issue Tracker and Wiki 5. Maintaining Your GitLab Instance 6. Webhooks, External Services, and the API 7. Using LDAP and OmniAuth Providers 8. GitLab CI A. Tips and Tricks Index

Logging in for the first time

When you have installed your server, you need to log in. GitLab comes with a built-in administrator account.

How to do it…

In this recipe, we will log in and create our own administrator account as follows:

  1. Go to your domain where GitLab is installed (that is, gitlab.example.com).
  2. Log in using the username root and password 5iveL!fe.
  3. You need to choose a new password; pick whatever you like.
  4. Log in with the new information.
  5. Go to the Admin area section, as shown in the following screenshot:
    How to do it…
  6. Navigate to Users | New User.
  7. Fill in the information to create your own user. Don't forget to check the Admin checkbox.
  8. Now, click on Create user.
    How to do it…

    An e-mail will be sent to the given e-mail address. This e-mail will contain the new password for this account.

  9. Log out from GitLab and log in with your new account.
  10. You need to choose a new password and log in again.
  11. Go to the Admin area section and click on Users.
  12. Click on Block for the administrator account.

How it works…

As GitLab ships with a default administrator account, this makes it a bit unsecure by default. Therefore, when you don't change anything about your setup, everyone will be able to log in.

To ensure that we have a secure GitLab installation, we created a new administrator account, and gave it an administrator access. We also want to be sure that the default shipped account is not useable anymore, so that's why we logged in with our own account and disabled the account given by GitLab.

We had to log out first, as GitLab does not allow us to disable the account that is currently logged in.

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