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

Added runbook todo and disabled forgejo-federated-image-publish

Browse source
This commit is contained in:
Clemens 2024-07-09 09:05:57 +02:00
parent 3be3486202
commit 545410767f
2 changed files with 11 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
.gitlab-ci.yml
View file

@ -123,9 +123,10 @@ forgejo-backup-image-publish:
script: script:
- cd infrastructure/backup && pyb image publish - cd infrastructure/backup && pyb image publish
forgejo-federated-image-publish: # This is currently not needed
<<: *img #forgejo-federated-image-publish:
<<: *tag_only # <<: *img
stage: image # <<: *tag_only
script: # stage: image
- cd infrastructure/federated && pyb image publish # script:
# - cd infrastructure/federated && pyb image publish

6
doc/Playbook_UpgradeFrom1.19To7.0.5.md → doc/Runbook_UpgradeFrom1.19To7.0.5.md
View file

@ -59,6 +59,8 @@
## Upgrade to 7.0.5 (no breaking changes) ## Upgrade to 7.0.5 (no breaking changes)
TODO: Upgrade to 8.0.0 instead after Release!
1. Scale down Forgejo Deployment: `k scale deployment forgejo --replicas=0` 1. Scale down Forgejo Deployment: `k scale deployment forgejo --replicas=0`
1. Delete app.ini: `k exec -it backup-restore-... -- rm /var/backups/gitea/conf/app.ini` 1. Delete app.ini: `k exec -it backup-restore-... -- rm /var/backups/gitea/conf/app.ini`
1. Set version to `7.0.5` with `k edit deployment forgejo` 1. Set version to `7.0.5` with `k edit deployment forgejo`
@ -74,9 +76,9 @@
1. The scope of all access tokens might (invisibly) have changed (in v1.20). Thus, rotate all tokens! 1. The scope of all access tokens might (invisibly) have changed (in v1.20). Thus, rotate all tokens!
1. Users should check their ssh keys: if they use rsa keys the minimum length should be 3072 bits! However, shorter keys should still work. 1. Users should check their ssh keys: if they use rsa keys the minimum length should be 3072 bits! However, shorter keys should still work.
# Known Errors ## Known Errors
## Error in v1.20.1-0 ### Error in v1.20.1-0
In the logs the following error can be found. This will be resolved automatically with the next upgrade (v1.21). In the logs the following error can be found. This will be resolved automatically with the next upgrade (v1.21).