Book Image

Practical DevOps

By : joakim verona
Book Image

Practical DevOps

By: joakim verona

Overview of this book

DevOps is a practical field that focuses on delivering business value as efficiently as possible. DevOps encompasses all the flows from code through testing environments to production environments. It stresses the cooperation between different roles, and how they can work together more closely, as the roots of the word imply—Development and Operations. After a quick refresher to DevOps and continuous delivery, we quickly move on to looking at how DevOps affects architecture. You'll create a sample enterprise Java application that you’ll continue to work with through the remaining chapters. Following this, we explore various code storage and build server options. You will then learn how to perform code testing with a few tools and deploy your test successfully. Next, you will learn how to monitor code for any anomalies and make sure it’s running properly. Finally, you will discover how to handle logs and keep track of the issues that affect processes
Table of Contents (17 chapters)
Practical DevOps
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Setting up a basic Git server


It's pretty easy to set up a basic Git server. While this is rarely enough in a large organization, it is a good exercise before moving on to more advanced solutions.

Let's first of all specify an overview of the steps we will take and the bits and pieces we will need to complete them:

  1. A client machine with two user accounts. The git and ssh packages should be installed.

    The SSH protocol features prominently as a base transport for other protocols, which is also is the case for Git.

    You need your SSH public keys handy. If you don't have the keys for some reason, use ssh-keygen to create them.

    Tip

    We need two users, because we will simulate two users talking to a central server. Make keys for both test users.

  2. A server where the SSH daemon is running.

    This can be the same machine as the one where you simulate the two different client users, or it can be another machine.

  3. A Git server user.

    We need a separate Git user who will handle the Git server functionality.

    Now, you...