Book Image

DevOps with Windows Server 2016

Book Image

DevOps with Windows Server 2016

Overview of this book

Delivering applications swiftly is one of the major challenges faced in fast-paced business environments. Windows Server 2016 DevOps is the solution to these challenges as it helps organizations to respond faster in order to handle the competitive pressures by replacing error-prone manual tasks using automation. This book is a practical description and implementation of DevOps principles and practices using the features provided by Windows Server 2016 and VSTS vNext. It jumps straight into explaining the relevant tools and technologies needed to implement DevOps principles and practices. It implements all major DevOps practices and principles and takes readers through it from envisioning a project up to operations and further. It uses the latest and upcoming concepts and technologies from Microsoft and open source such as Docker, Windows Container, Nano Server, DSC, Pester, and VSTS vNext. By the end of this book, you will be well aware of the DevOps principles and practices and will have implemented all these principles practically for a sample application using the latest technologies on the Microsoft platform. You will be ready to start implementing DevOps within your project/engagement.
Table of Contents (20 chapters)
DevOps with Windows Server 2016
Credits
About the Author
Acknowledgments
About the Reviewer
Acknowledgments
www.PacktPub.com
Customer Feedback
Preface

Git 101


As mentioned before, Git is a Distributed Version Control Management System. Any folder on disk can be a Git repository. The only requirement to be a Git repository is that it should be Initialized or Cloned using the Git command-line. A Git repository contains files and folders along with a complete history of changes made to them. It also contains information about active, passive branches along with tags. All files and folders under the control of the Git repository are collectively called a working tree.

The Git repository can be either remote or local. Remote repositories are repositories hosted on the Internet and can be accessed from anywhere while local repositories are repositories hosted on the developer's workstation and accessible only to that developer. Remote repositories can be cloned as local repositories. When remote repositories are cloned, all files and folders (also known as the working tree) along with the entire repository history are copied to the developer...