[Feature] The stack/info page should detect *compose.override.yml files and allow us to edit them #1087

New Issue

GiteaMirror · 2026-03-22T17:09:08-05:00

GiteaMirror commented

2026-03-22 17:09:08 -05:00

Originally created by @itsmaxymoo on GitHub (Apr 5, 2025).

When starting a stack in Komodo, the associated docker-compose.override.yml works as expected. If I enter both compose and override.yml files into the Komodo interface, it marks the stack as unhealthy (?). I use override.yml files to apply portable customizations (reverse proxy, bind volumes, etc...) to vendored compose files. Ideally, the compose.yml editor would detect override files, as well.

Originally created by @itsmaxymoo on GitHub (Apr 5, 2025). When starting a stack in Komodo, the associated docker-compose.override.yml works as expected. If I enter both compose and override.yml files into the Komodo interface, it marks the stack as unhealthy (?). I use override.yml files to apply portable customizations (reverse proxy, bind volumes, etc...) to vendored compose files. Ideally, the compose.yml editor would detect override files, as well.

GiteaMirror closed this issue

2026-03-22 17:09:09 -05:00

GiteaMirror commented

2026-03-22 17:09:10 -05:00

@mbecker20 commented on GitHub (Apr 5, 2025):

Lets start with editing - did you add both the main compose file and the override compose file in the File Paths configuration? If this is done, it should show both files on the Info page with their associated paths, and allow you to edit both.

@mbecker20 commented on GitHub (Apr 5, 2025): Lets start with editing - did you add both the main compose file and the override compose file in the File Paths configuration? If this is done, it should show both files on the Info page with their associated paths, and allow you to edit both.

GiteaMirror commented

2026-03-22 17:09:10 -05:00

@itsmaxymoo commented on GitHub (Apr 7, 2025):

@mbecker20 Yes. It appears that it requires you to full stop and then restart the stack, and then it will no longer show up as "unhealthy". This is good enough for me. I'm unfamiliar with rust, but if you give me a quick rundown of the relevant files I can try and add the custome OIDC username parameter.

@itsmaxymoo commented on GitHub (Apr 7, 2025): @mbecker20 Yes. It appears that it requires you to full stop and then restart the stack, and then it will no longer show up as "unhealthy". This is good enough for me. I'm unfamiliar with rust, but if you give me a quick rundown of the relevant files I can try and add the custome OIDC username parameter.

GiteaMirror commented

2026-03-22 17:09:10 -05:00

@mbecker20 commented on GitHub (Apr 7, 2025):

@itsmaxymoo The OIDC username is handled here: https://github.com/moghtech/komodo/blob/1.17.1/bin/core/src/auth/oidc/mod.rs#L230

If you do PR, base it on 1.17.1, so it can be included in next release.

@mbecker20 commented on GitHub (Apr 7, 2025): @itsmaxymoo The OIDC username is handled here: https://github.com/moghtech/komodo/blob/1.17.1/bin/core/src/auth/oidc/mod.rs#L230 If you do PR, base it on 1.17.1, so it can be included in next release.

GiteaMirror referenced this issue

2026-04-11 10:29:33 -05:00

[GH-ISSUE #1087] [Feature] Allow New User Registration only from OIDC #2621

GiteaMirror referenced this issue

2026-04-11 10:43:06 -05:00

[PR #1321] Add per-provider user registration control #3019

GiteaMirror referenced this issue

2026-04-13 15:10:59 -05:00

[GH-ISSUE #1087] [Feature] Allow New User Registration only from OIDC #3766

GiteaMirror referenced this issue

2026-04-13 15:20:57 -05:00

[PR #1321] Add per-provider user registration control #4167