WIP: update some deprecated configs #51

2026-05-06T15:07:15Z

ammaratef45 commented

2026-05-06 15:07:15 +00:00

Admin dashboard throws these warnings:

Startup warnings:

    Deprecation: config option `[log].ENABLE_XORM_LOG` presents, please use `[log].logger.xorm.MODE` instead because this fallback will be/has been removed in 1.21
    Deprecation: config option `[mailer].MAILER_TYPE` presents, please use `[mailer].PROTOCOL` instead because this fallback will be/has been removed in v1.19.0

Pending (help appreciated):

testing (I don't have a gitea instance to test on and too lazy to setup a test instance for now)
response/clarification on this question; making sure removing ENABLE_XORM_LOG=false while keeping LOG_SQL=false (default) has the same effect as the legacy config

references used:

Admin dashboard throws these warnings: ``` Startup warnings: Deprecation: config option `[log].ENABLE_XORM_LOG` presents, please use `[log].logger.xorm.MODE` instead because this fallback will be/has been removed in 1.21 Deprecation: config option `[mailer].MAILER_TYPE` presents, please use `[mailer].PROTOCOL` instead because this fallback will be/has been removed in v1.19.0 ``` Pending (help appreciated): - [ ] testing (I don't have a gitea instance to test on and too lazy to setup a test instance for now) - [ ] response/clarification on [this question](https://forum.gitea.com/t/disable-xorm-logging-in-v1-21/12082); making sure removing `ENABLE_XORM_LOG=false` while keeping `LOG_SQL=false` (default) has the same effect as the legacy config references used: - https://docs.gitea.com/administration/config-cheat-sheet - https://docs.gitea.com/administration/logging-config

ammaratef45 added 1 commit 2026-05-06 15:07:15 +00:00

update some deprecated configs c2e1be0211

decentral1se commented

2026-05-06 21:38:16 +00:00

Nice. Not in a position to test myself now also but it LGTM!

notplants commented

2026-05-12 18:19:33 +00:00

fwiw: today I've been trying to upgrade git.coopcloud.tech to use the latest recipe version. and running into a failure that is causing a rollback during upgrade.

$ abra app upgrade git.coopcloud.tech
? please select an upgrade (version: 3.4.0+1.24.2-rootless): 3.5.2+1.24.2-rootless
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃                 UPGRADE OVERVIEW                 ┃
┃                                                  ┃
┃ DOMAIN                https://git.coopcloud.tech ┃
┃ RECIPE                gitea                      ┃
┃ SERVER                swarm-0.coopcloud.tech     ┃
┃ CONFIG                compose.yml                ┃
┃                       compose.mariadb.yml        ┃
┃                       compose.smtp.yml           ┃
┃                                                  ┃
┃ CURRENT DEPLOYMENT    3.4.0+1.24.2-rootless      ┃
┃ ENV VERSION           3.5.2+1.24.2-rootless      ┃
┃ NEW DEPLOYMENT        3.5.2+1.24.2-rootless      ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
WARN no release notes available for 3.5.2+1.24.2-rootless
? proceed? Yes
INFO initialising deployment
INFO polling deployment status
app: rolled back (retries: 0, healthcheck: healthy)
db: succeeded (retries: 0, healthcheck: ?)
FATA deploy failed 🛑
logs: /home/notplants/.abra/logs/swarm-0.coopcloud.tech/git_coopcloud_tech_2026-05-12T181804Z

it is strange that the app is passing the healtcheck, but still moving to "rolled back". I haven't see this before. haven't found anything in logs. currently stumped

fwiw: today I've been trying to upgrade git.coopcloud.tech to use the latest recipe version. and running into a failure that is causing a rollback during upgrade. ``` $ abra app upgrade git.coopcloud.tech ? please select an upgrade (version: 3.4.0+1.24.2-rootless): 3.5.2+1.24.2-rootless ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ UPGRADE OVERVIEW ┃ ┃ ┃ ┃ DOMAIN https://git.coopcloud.tech ┃ ┃ RECIPE gitea ┃ ┃ SERVER swarm-0.coopcloud.tech ┃ ┃ CONFIG compose.yml ┃ ┃ compose.mariadb.yml ┃ ┃ compose.smtp.yml ┃ ┃ ┃ ┃ CURRENT DEPLOYMENT 3.4.0+1.24.2-rootless ┃ ┃ ENV VERSION 3.5.2+1.24.2-rootless ┃ ┃ NEW DEPLOYMENT 3.5.2+1.24.2-rootless ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ WARN no release notes available for 3.5.2+1.24.2-rootless ? proceed? Yes INFO initialising deployment INFO polling deployment status app: rolled back (retries: 0, healthcheck: healthy) db: succeeded (retries: 0, healthcheck: ?) FATA deploy failed 🛑 logs: /home/notplants/.abra/logs/swarm-0.coopcloud.tech/git_coopcloud_tech_2026-05-12T181804Z ``` it is strange that the app is passing the healtcheck, but still moving to "rolled back". I haven't see this before. haven't found anything in logs. currently stumped

decentral1se commented

2026-05-13 09:37:58 +00:00

You can try streaming the healthcheck logs, there is some obscure incantation for this which you can combine with watch. We never quite managed to get that output into the UI or the logs as far as I can remember... good luck!

You can try streaming the healthcheck logs, there is some obscure incantation for this which you can combine with `watch`. We never quite managed to get that output into the UI or the logs as far as I can remember... good luck!

👍 1

notplants commented

2026-05-18 16:44:43 +00:00

I am debugging this further, but moved it into an issue here as its not directly related to this PR

I am debugging this further, but moved it into an issue [here](https://git.coopcloud.tech/coop-cloud/gitea/issues/52) as its not directly related to this PR

Checking for merge conflicts…

This pull request is marked as a work in progress.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin config-update:config-update

git checkout config-update

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/gitea#51