mirror of
https://github.com/semaphoreci/book-cicd-docker-kubernetes.git
synced 2026-08-18 19:46:48 +00:00
Start writing Introduction
This commit is contained in:
@@ -1,11 +1,11 @@
|
||||
BUILD = build
|
||||
BOOKNAME = CICD_with_Docker_Kubernetes_Semaphore
|
||||
TITLE = title.txt
|
||||
CHAPTERS = ch01.md ch02.md ch03.md ch04.md
|
||||
CHAPTERS = chapters/01-introduction.md
|
||||
|
||||
all: book
|
||||
|
||||
book: pdf #epub html
|
||||
book: pdf #epub
|
||||
|
||||
clean:
|
||||
rm -r $(BUILD)
|
||||
@@ -16,4 +16,4 @@ $(BUILD)/pdf/$(BOOKNAME).pdf: $(TITLE) $(CHAPTERS)
|
||||
mkdir -p $(BUILD)/pdf
|
||||
pandoc -o $@ $^
|
||||
|
||||
.PHONY: all book clean pdf #epub html
|
||||
.PHONY: all book clean pdf #epub
|
||||
|
||||
@@ -0,0 +1,35 @@
|
||||
\newpage
|
||||
|
||||
# Introduction
|
||||
|
||||
TODO: The fine print, copyright, date of update, brought to you by etc.
|
||||
|
||||
\newpage
|
||||
|
||||
## Preface
|
||||
|
||||
TODO: Short Motivational introduction.
|
||||
|
||||
### Who Is This Book For, and What Does It Cover?
|
||||
|
||||
The main goal of this book is to provide a practical roadmap to continuous delivery for software development teams who have decided to use Docker containers to package their code and Kubernetes to run it.
|
||||
|
||||
We don't spend much time explaining why you should, or should not use container technologies to ship your applications. We also can't provide a better general reference to using Docker and Kubernetes than their respective official documentation.
|
||||
|
||||
We assume that you're fairly new to the container technology stack, and that your goal is to establish a standardized and fully automated build, test and release process.
|
||||
|
||||
We believe that both technology leaders and individual contributors will benefit from reading this book.
|
||||
|
||||
If you are a CTO or otherwise ultimately responsible for effectively delivering working software to customers, this book will provide you with a clear vision of what a reliable CI/CD pipeline to Kubernetes looks like, and what it takes to build one.
|
||||
|
||||
If you are a developer or systems administrator, besides understanding the big picture, you will also find working code and configuration that you can reuse in your own projects.
|
||||
|
||||
TODO: Summary of each chapter. One paragraph, or sentence, for each.
|
||||
|
||||
Chapter 1, "Using Docker for Development and Continuous Delivery", outlines the key benefits of using Docker and provides a detailed roadmap to adopting it.
|
||||
|
||||
Chapter 2, ""
|
||||
|
||||
## About the Authors
|
||||
|
||||
TODO: A paragraph for each person.
|
||||
Reference in New Issue
Block a user