Merge branch 'docs/update' of kosmos/gitea.kosmos.org into master
This commit is contained in:
commit
43ad6f842b
|
@ -41,3 +41,31 @@ 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.
|
||||
|
||||
$ docker pull gitea/gitea
|
||||
$ docker tag gitea/gitea:latest kosmosorg/gitea:production
|
||||
$ docker push kosmosorg/gitea
|
||||
|
||||
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
|
||||
|
|
Reference in New Issue