Document how to update Gitea itself #12
Labels
No Label
bug
dev environment
docs
duplicate
enhancement
feature
idea
invalid
kredits-1
kredits-2
kredits-3
ops
question
security
ui/ux
wontfix
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/gitea.kosmos.org#12
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There's currently a container image from Docker Hub in use, but no documentation on how it got there, or how to deploy a new version of Gitea.
We're behind a few releases that fixed some security issues, and they release quite often, so it should be easy for anyone with access to update the deployment.
Until now we were deploying from https://hub.docker.com/r/5apps/gitea/tags/ (because we needed unreleased fixes to Let's Encrypt). We can now switch to the 1.7 release from the official images (https://hub.docker.com/r/gitea/gitea/tags/)
The Kosmos organization is already taken on Docker (https://hub.docker.com/u/kosmos, created by someone on July 27, 2015). I just tried, 67p is too short for an org name (has to be at least 4 letters).
Meanwhile I'm documenting how I pushed the latest tag to our gitea repo on 5apps' Docker Hub
I just pushed that change to master and applied it.
This has long been documented in
doc/
.