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

[Skip-CI] Clarifications

Browse source
This commit is contained in:
patdyn 2024-07-05 10:29:51 +02:00
parent eb33cf5e0b
commit b9d38bdeed
1 changed files with 46 additions and 43 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

89
doc/Upgrading.md
View file

@ -25,18 +25,17 @@ You may want to update your c4k-forgejo resources to reflect the changes made on
### Config related issues with c4k-forgejo v3.2.2 ### Config related issues with c4k-forgejo v3.2.2
- oauth2: ENABLED instead of ENABLE - oauth2: ENABLED instead of ENABLE
- `FORGEJOoauth2ENABLED: "true"` - `FORGEJO__oauth2__ENABLED: "true"`
- 2024/07/02 13:16:17 ...g/config_provider.go:329:deprecatedSetting() [E] Deprecated config option `[log]` `ROUTER` present. Use `[log]` `logger.router.MODE` i - 2024/07/02 13:16:17 ...g/config_provider.go:329:deprecatedSetting() [E] Deprecated config option `[log]` `ROUTER` present. Use `[log]` `logger.router.MODE` i
nstead. This fallback will be/has been removed in 1.21 nstead. This fallback will be/has been removed in 1.21
- `FORGEJOlog_0x2E_logger_0x2E_routerMODE: console, file` - `FORGEJO__log_0x2E_logger_0x2E_router__MODE: console, file`
- 2024/07/02 13:16:17 ...g/config_provider.go:329:deprecatedSetting() [E] Deprecated config option `[service]` `EMAIL_DOMAIN_WHITELIST` present. Use `[service] - 2024/07/02 13:16:17 ...g/config_provider.go:329:deprecatedSetting() [E] Deprecated config option `[service]` `EMAIL_DOMAIN_WHITELIST` present. Use `[service]
` `EMAIL_DOMAIN_ALLOWLIST` instead. This fallback will be/has been removed in 1.21 ` `EMAIL_DOMAIN_ALLOWLIST` instead. This fallback will be/has been removed in 1.21
- `FORGEJOserviceEMAIL_DOMAIN_ALLOWLIST:` - `FORGEJO__service__EMAIL_DOMAIN_ALLOWLIST:`
- 2024/07/02 13:16:17 ...g/config_provider.go:329:deprecatedSetting() [E] Deprecated config option `[mailer]` `MAILER_TYPE` present. Use `[mailer]` `PROTOCOL` - 2024/07/02 13:16:17 ...g/config_provider.go:329:deprecatedSetting() [E] Deprecated config option `[mailer]` `MAILER_TYPE` present. Use `[mailer]` `PROTOCOL`
instead. This fallback will be/has been removed in v1.19.0 instead. This fallback will be/has been removed in v1.19.0
- ...es/setting/mailer.go:133:loadMailerFrom() [E] Deprecated fallback `[mailer]` `PROTOCOL = smtp+startls` present. Use `[mailer]` `PROTOC - ...es/setting/mailer.go:133:loadMailerFrom() [E] Deprecated fallback `[mailer]` `PROTOCOL = smtp+startls` present. Use `[mailer]` `PROTOCOL = smtp+starttls`` instead. This fallback will be removed in v1.19.0
OL = smtp+starttls`` instead. This fallback will be removed in v1.19.0 - `FORGEJO__mailer__PROTOCOL: smtp+starttls`
- `FORGEJOmailerPROTOCOL: smtp+starttls`
- starttls instead of startls - starttls instead of startls
### Breaking Changes ### Breaking Changes
@ -107,7 +106,7 @@ You may want to update your c4k-forgejo resources to reflect the changes made on
- benutzen wir: - benutzen wir:
- [/repos/{owner}/{repo}/releases](https://code.forgejo.org/api/swagger/#/repository/repoListReleases) - [/repos/{owner}/{repo}/releases](https://code.forgejo.org/api/swagger/#/repository/repoListReleases)
- [`/repos/{owner}/{repo}/push_mirrors`](https://code.forgejo.org/api/swagger/#/repository/repoListPushMirrors) - [/repos/{owner}/{repo}/push_mirrors](https://code.forgejo.org/api/swagger/#/repository/repoListPushMirrors)
- Application profiling - Application profiling
##### repos ##### repos
@ -121,14 +120,14 @@ You may want to update your c4k-forgejo resources to reflect the changes made on
### Vor dem Upgrade ### Vor dem Upgrade
- host cert used for auth? - host cert used for auth? - nein
- benutzen wir webhooks? - benutzen wir webhooks? - nein
- benutzen wir: - benutzen wir:
- [/repos/{owner}/{repo}/releases](https://code.forgejo.org/api/swagger/#/repository/repoListReleases) - [/repos/{owner}/{repo}/releases](https://code.forgejo.org/api/swagger/#/repository/repoListReleases) - ja
- [`/repos/{owner}/{repo}/push_mirrors`](https://code.forgejo.org/api/swagger/#/repository/repoListPushMirrors) - [`/repos/{owner}/{repo}/push_mirrors`](https://code.forgejo.org/api/swagger/#/repository/repoListPushMirrors) - nein
- Application profiling - Application profiling - nein
- do we have repo descriptions? - do we have repo descriptions?
- https://codeberg.org/forgejo/forgejo/commit/1075ff74b5050f671c5f9824ae39390230b3c85d - https://codeberg.org/forgejo/forgejo/commit/1075ff74b5050f671c5f9824ae39390230b3c85d - ja
### Upgrade plan ### Upgrade plan
@ -136,53 +135,57 @@ TEST kennzeichnet Aktionen die nur für den Testserver gelten und in PROD ignori
PROD kennzeichnet Aktionen die nur für den Testserver gelten und in TEST ignoriert werden. PROD kennzeichnet Aktionen die nur für den Testserver gelten und in TEST ignoriert werden.
Generelle Übersicht zu Upgrades: https://forgejo.org/docs/latest/admin/upgrade/ Generelle Übersicht zu Upgrades: https://forgejo.org/docs/latest/admin/upgrade/
- Forgejo server aufsetzen mit alter version - Forgejo Server aufsetzen mit c4k-forgejo v3.2.2
- Enthält Forgejo v1.19
- TEST - TEST
- Alte remote id löschen - Alte remote id löschen
- ssh-keygen -f "/home/erik/.ssh/known_hosts" -R "repo.test.meissa.de" - `ssh-keygen -f "/home/${USER}/.ssh/known_hosts" -R "repo.test.meissa.de"`
- auf server ssh'en - Auf server ssh'en
- forgejo pod runterfahren - Forgejo pod runterfahren
- `k scale deployment forgejo --replicas=0` - `k scale deployment forgejo --replicas=0`
- install lock aus - Install lock aus
- `k edit cm forgejo-env` - `k edit cm forgejo-env`
- set to `FORGEJOsecurityINSTALL_LOCK: "false"` - Set to `FORGEJO__security__INSTALL_LOCK: "false"`
- forgejo pod hochfahren - Forgejo pod hochfahren
- `k scale deployment forgejo --replicas=1` - `k scale deployment forgejo --replicas=1`
- admin test oder prod admin anlegen und forgejo installieren - Admin test oder prod admin anlegen und forgejo installieren
- `gopass show server/meissa/forgejo-test` bzw `-prod` - `gopass show server/meissa/forgejo-test` bzw `-prod`
- forgejo pod runterfahren - Forgejo pod runterfahren
- install lock an - Install lock an
- set to `FORGEJOsecurityINSTALL_LOCK: "true"` - Set to `FORGEJO__security__INSTALL_LOCK: "true"`
- TEST - TEST
- forgejo pod hochfahren - Forgejo pod hochfahren
- einloggen - Einloggen
- ssh keys anlegen - Ssh keys anlegen
- ed_xyz - ed_xyz
- rsa mit 2048 - rsa mit 2048
- rsa mit 4096 - rsa mit 4096
- Repos anlegen - Repos anlegen
- forgejo pod runterfahren - Forgejo pod runterfahren
- PROD - PROD
- backup pod hochfahren - Backup pod hochfahren
- `k scale deployment backup-restore --replicas=1` - `k scale deployment backup-restore --replicas=1`
- backups zurückspielen - Backups zurückspielen
- im backup pod vorhandene app.ini's löschen bzw umbenennen - Im backup pod vorhandene app.ini's löschen bzw umbenennen
- backup pod runterfahren - Backup pod runterfahren
- `k scale deployment backup-restore --replicas=0` - `k scale deployment backup-restore --replicas=0`
- im deployment image ver auf 7.0.4 setzen - Im Forgejo Deployment die Image Ver auf 7.0.4 setzen
- `k edit deployment.apps forgejo` - `k edit deployment.apps forgejo`
- configmap updaten - Configmap updaten:
- double check ob install lock an - Double check ob install lock an
- siehe Config related errors oben - `FORGEJO__oauth2__ENABLED: "true"`
- `FORGEJO__log_0x2E_logger_0x2E_router__MODE: console, file`
- `FORGEJO__service__EMAIL_DOMAIN_ALLOWLIST:`
- `FORGEJO__mailer__PROTOCOL: smtp+starttls`
- TEST - TEST
- backup pod hochfahren - Backup pod hochfahren
- im backup pod vorhandene app.ini's löschen bzw umbenennen - Im backup pod vorhandene app.ini's löschen bzw umbenennen
- backup pod runterfahren - Backup pod runterfahren
- `k scale deployment backup-restore --replicas=0` - `k scale deployment backup-restore --replicas=0`
- forgejo pod hochscalen - Forgejo pod hochscalen
- Migrations happen automatically - Migrations happen automatically
- `/admin` page and click run Sync missed branches from git data to databases - `/admin` page and click run Sync missed branches from git data to databases
- and **Sync missed tags ...* - and **Sync missed tags ...*
- rsa keys with size 2048 can not be added anymore. However, it seems they still can be used if they are on the server - Rsa keys with size 2048 can not be added anymore. However, it seems they still can be used if they are on the server
- team members having app tokens need to recreate them with proper scopes - Team members having app tokens need to recreate them with proper scopes
- add analytics: https://forgejo.org/docs/latest/admin/customization/ - Add analytics: https://forgejo.org/docs/latest/admin/customization/