Add a new doc for Lock (#143)

* Add a new doc for lock

* Fix deployment docs

* Fix perm docs

* Fix the version in the installation doc

Author: Noah Hanjun Lee

docs/concepts/deployment.md

@@ -4,14 +4,22 @@ Gitploy provides two types of deployment: Deploy and Rollback.
 
 ## Deploy
 
-Deploying is the primary feature of Gitploy. When you deploy, you have to select the environment and the `ref`: for the environment, you can choose one of the environments listed in the `deploy.yml`, and for the `ref`, you can choose one of commit, branch, and tag.
+Deploying is the primary feature of Gitploy. When you deploy, you have to select the environment and the reference. The environment is one of the environments defined in the configuration file (i.e., deploy.yml). And for reference, you can choose one of commit, branch, and tag.
 
-With approval, Gitploy waits until it matches the required approving approvals. So you have to confirm to deploy after approval.
+When you deploy the ref, Gitploy post the deployment to GitHub, and Github dispatch the event to external services.
+
+Figure) Deploy
+
+![deploy](../images/deploy.png)
 
 ## Rollback
 
-Rollback is the best way to recover while you fix the problems. Gitploy supports the rollback, and you can choose one of the successful deployments to rollback. 
+Rollback is the best way to recover while you fix the problems, and Gitploy supports the rollback. You can choose one of the deployed references for the environment to roll back. 
+
+When you roll back to the specific reference, Gitploy posts a new deployment with the reference from the rollbacked deployment. *Note that if the reference of the rollbacked deployment is a branch, Gitploy automatically references the commit SHA to avoid deploying the head of the branch.*
 
 For best practice, you should lock the environment to block deploying by others until finishing to fix the problems. Gitploy provide the 'lock' feature in UI and Chatops.
 
-*Note that if the ref of the selected deployment is a branch, Gitploy automatically references the commit SHA to prevent deploying the head of the branch.*
+Figure) Rollback
+
+![rollback](../images/rollback.png)

docs/concepts/lock.md

@@ -0,0 +1,9 @@
+# Lock
+
+The worst thing that can happen is someone deploys to the same repository during an incident. The lock helps with this. We provide the locking system to block deployments that are going out to the environment. 
+
+You can lock the environment simply by clicking the button in the UI.
+
+Figure) Lock
+
+![lock](../images/lock.png)

docs/concepts/permission.md

@@ -11,8 +11,14 @@ Here are capabilities for each permission:
 
 * **Read** - Users can read all activities that happened in the repository, such as deployments, approvals. And users are also capable of responding to the approval.
 
-* **Write** - Users can lock, deploy, and rollback for the `REF`. 
+* **Write** - Users can lock, deploy, and rollback. 
 
 * **Admin** - Users can configures the repository, such as activating.
 
-Of course, write and admin permission cover the ability of read permission.
+Of course, write and admin permission cover the ability of read permission.
+
+## System admin
+
+The permission of the system admin can manage members of Gitploy. 
+ 
+You can identify admin members by [GITPLOY_ADMIN_USERS](../references/GITPLOY_ADMIN_USERS.md).

docs/images/deploy-commit.png

@@ -33,11 +33,11 @@ In the 'Deploy' tab, you can find the deployment form. In this example, we'll de
 
 Figure) Gitploy Deployment Form
 
-![Deploy commit](../images/deploy-commit.png)
+![deploy](../images/deploy.png)
 
 ## Step 4: Deployment Event
 On the deployment page of Github, you can find the new Github deployment at the top. In production, the deployment tool should listen to the event and start to deploy. You can reference the [community](https://github.com/gitploy-io/gitploy/discussions/categories/share-pipeline) and it is sharing how to implement the whole pipeline.
 
 Figure) Github deployment
 
-![Github deployment](../images/github-deployment.png)
+![Github deployment](../images/github-deployment.png)

docs/images/deploy.png

@@ -41,7 +41,7 @@ Required string value configures the GitHub OAuth client secret. This is used to
 The server is distributed as a Docker image. The image is self-contained and does not have any external dependencies. We recommend to use the last version.
 
 ```
-docker pull gitployio/gitploy:0.3
+docker pull gitployio/gitploy:0.1
 ```
 
 The server container can be started with the below command. The container is configured through environment variables.
@@ -58,7 +58,7 @@ docker run \
   --restart=always \
   --detach=true \
   --name=gitploy \
-  gitployio/gitploy:0.3
+  gitployio/gitploy:0.1
 ```
 
 ### Kubernetes
@@ -105,7 +105,7 @@ spec:
     spec:
       containers:
         - name: gitploy-server
-          image: "gitployio/gitploy:0.3"
+          image: "gitployio/gitploy:0.1"
           imagePullPolicy: IfNotPresent
           ports:
             - name: http

docs/images/lock.png

@@ -13,6 +13,7 @@ nav:
     - "How it works": concepts/how-it-work.md
     - "deploy.yml": concepts/deploy.yml.md
     - Deployment: concepts/deployment.md
+    - Lock: concepts/lock.md
     - Permission: concepts/permission.md
     - "Self-hosted Server": concepts/self-hosted-server.md
     - Chatops: concepts/chatops.md