me/c4k-forgejo
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

update Upgrading documentation to be gitea specific

Browse source
This commit is contained in:
bom 2022-11-02 13:15:15 +01:00
parent 02bb23d107
commit bf16cdd02c
1 changed files with 8 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
doc/Upgrading.md
View file

@ -1,22 +1,21 @@
# Release process # Upgrading process
## adhoc (on kubernetes cluster) ## adhoc (on kubernetes cluster)
Make sure you've got your gitea admin credentials. Make sure you've got your gitea admin credentials.
``` bash ``` bash
kubectl edit deployments [website-pod-deployment-name] kubectl edit configmap gitea-env
# make sure INSTALL_LOCK under security is set to true to disable the installation screen
# save and exit
kubectl edit deployments gitea
# search for your current gitea version, e.g. 1.17.0 # search for your current gitea version, e.g. 1.17.0
# replace with new version # replace with new version
# save and exit # save and exit
kubectl scale deployment meissa-io-deployment --replicas=0 kubectl scale deployment gitea --replicas=0
kubectl scale deployment meissa-io-deployment --replicas=1 kubectl scale deployment gitea --replicas=1
``` ```
Visit your gitea url.
The inital installation screen should be visible.
Enter your admin credentials.
You now should be logged into the admin account with all repos visible. You now should be logged into the admin account with all repos visible.
You may want to update your c4k-gitea resources to reflect the changes made on the cluster. You may want to update your c4k-gitea resources to reflect the changes made on the cluster.