Book Image

TypeScript Design Patterns

By : Vilic Vane
Book Image

TypeScript Design Patterns

By: Vilic Vane

Overview of this book

In programming, there are several problems that occur frequently. To solve these problems, there are various repeatable solutions that are known as design patterns. Design patterns are a great way to improve the efficiency of your programs and improve your productivity. This book is a collection of the most important patterns you need to improve your applications’ performance and your productivity. The journey starts by explaining the current challenges when designing and developing an application and how you can solve these challenges by applying the correct design pattern and best practices. Each pattern is accompanied with rich examples that demonstrate the power of patterns for a range of tasks, from building an application to code testing. We’ll introduce low-level programming concepts to help you write TypeScript code, as well as work with software architecture, best practices, and design aspects.
Table of Contents (15 chapters)
TypeScript Design Patterns
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

Deployment automation


Rather than a version control tool, Git is also popular for relatively simple deployment automation. And in this section, we'll get our hands on and configure automated deployment based on Git.

Passive deployment based on Git server side hooks

The idea of passive deployment is simple: when a client pushes commits to the bare repository on the server, a post-receive hook of Git will be triggered. And thus we can add scripts checking out changes and start deployment.

The elements involved in the Git deployment solution on both the client and server sides includes:

To make this mechanism work, we need to perform the following steps:

  1. Create a bare repository on the server with the following command:

          $ mkdir deployment.git
          $ cd deployment.git
          $ git init --bare
    

    Note

    A bare repository usually has the extension .git and can be treated as a centralized place for sharing purposes. Unlike normal repositories, a bare repository does not have the working copy of source...