From 346c715904271229dc56690a7ecbd7c453be7d5b Mon Sep 17 00:00:00 2001 From: Anchor Date: Sun, 21 Dec 2014 21:21:21 -0800 Subject: [PATCH] Fix grammar and translations for introduction of 12.2.md --- en/12.3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/12.3.md b/en/12.3.md index 0d439c39..e4e897c9 100644 --- a/en/12.3.md +++ b/en/12.3.md @@ -1,6 +1,6 @@ # 12.3 Deployment -After completion of the development program, we now want to deploy Web applications, but how do we deploy these applications do ? Because after compiling Go programs is an executable file, written a C program using daemon readers must know you can achieve the perfect background program runs continuously, but still not perfect at present Go realization daemon, therefore, for a Go application deployment, we can use third-party tools to manage, there are many third-party tools, such as Supervisord, upstart, daemon tools, etc. This section describes my own system using current tools Supervisord. +When our web application is finally production ready, what are the steps necessary to get it deployed? In Go, an executable file encapsulating our application is created after we compile our programs. Programs written in C can run perfectly as background daemon processes, however Go does not yet have native support for daemons. The good news is that we can use third party tools to help us manage the deployment of our Go applications, examples of which are Supervisord, upstart and daemontools, among others. This section will introduce you to some basics of the Supervisord process control system. ## Daemon