From 8a2d491e45981dad3e6f3403afa51ae2f0ac9dab Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Greg=20Kar=C3=A9kinian?= <greg@karekinian.com>
Date: Tue, 8 Jan 2019 12:14:41 +0100
Subject: [PATCH 1/2] Add documentation about updating Gitea

---
 doc/kubernetes.md | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/doc/kubernetes.md b/doc/kubernetes.md
index b4157e8..fbc3015 100644
--- a/doc/kubernetes.md
+++ b/doc/kubernetes.md
@@ -41,3 +41,27 @@ Kubernetes before uploading them again. This is done by this script:
 > @whitecolor, in your case you should be fine by clearing `PV.Spec.ClaimRef.UID` in the PV. Only the re-created PVC (with any UID) can then use the PV. And it's your responsibility that only the right person can craft appropriate PVC so nobody can steal your data.
 
 https://github.com/kubernetes/kubernetes/issues/48609#issuecomment-314066616
+
+## Update Gitea
+
+### Released version
+
+Change the image for the gitea-server container
+(`kubernetes/gitea-server.yaml`) to `gitea/gitea:TAG`, for example:
+`gitea/gitea:1.7.0-rc2`
+
+### Unreleased version
+
+This is useful to deploy features that are in master but not yet in a release.
+
+TODO: Create an org on Docker Hub (kosmos is already taken and 67p is too short)
+
+    $ docker pull gitea/gitea
+    $ docker tag gitea/gitea:latest $ORG/gitea:latest
+    $ docker push $ORG/gitea
+
+Set the image for the gitea-server container to `$ORG/gitea:latest`, or run 
+this command to force a deployment if it is already set to it
+
+    $ kubectl patch deployment gitea-server -p "{\"spec\":{\"template\":{\"metadata\":{\"annotations\":{\"date\":\"`date +'%s'`\"}}}}}"
+

From 34068bc7acd2b45ac8a00dff1980850355c69b02 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Greg=20Kar=C3=A9kinian?= <greg@karekinian.com>
Date: Fri, 25 Jan 2019 16:52:17 +0100
Subject: [PATCH 2/2] Add docs about building our own images

---
 doc/kubernetes.md | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/doc/kubernetes.md b/doc/kubernetes.md
index fbc3015..55ef506 100644
--- a/doc/kubernetes.md
+++ b/doc/kubernetes.md
@@ -54,14 +54,18 @@ Change the image for the gitea-server container
 
 This is useful to deploy features that are in master but not yet in a release.
 
-TODO: Create an org on Docker Hub (kosmos is already taken and 67p is too short)
-
     $ docker pull gitea/gitea
-    $ docker tag gitea/gitea:latest $ORG/gitea:latest
-    $ docker push $ORG/gitea
+    $ docker tag gitea/gitea:latest kosmosorg/gitea:production
+    $ docker push kosmosorg/gitea
 
-Set the image for the gitea-server container to `$ORG/gitea:latest`, or run 
+Set the image for the gitea-server container to `kosmosorg/gitea:latest`, or run 
 this command to force a deployment if it is already set to it
 
     $ kubectl patch deployment gitea-server -p "{\"spec\":{\"template\":{\"metadata\":{\"annotations\":{\"date\":\"`date +'%s'`\"}}}}}"
 
+### Build our own image
+
+At the root of the [https://github.com/go-gitea/gitea](gitea repo)
+
+    $ DOCKER_TAG=production DOCKER_IMAGE=kosmosorg/gitea make docker # builds and tags kosmosorg/gitea:production locally
+    $ docker push kosmosorg/gitea