Originally created by @cyndane31 on GitHub (Jun 17, 2025).
I currently use compose service profiles to control the webui's for a few different backend services, namely my various databases. As far as I can tell, the only way to control deployment of a specific profile is using Extra Args to specify --profile=xxx. A UI element to control the deployed profile near the rest of the control elements would be a nice small QoL improvement.
Originally created by @cyndane31 on GitHub (Jun 17, 2025).
I currently use compose service profiles to control the webui's for a few different backend services, namely my various databases. As far as I can tell, the only way to control deployment of a specific profile is using Extra Args to specify --profile=xxx. A UI element to control the deployed profile near the rest of the control elements would be a nice small QoL improvement.
I was just looking into this and would also appreciate native profile support. For anyone trying to get this to work in the meantime, here's what I discovered.
Extra Args didn't work (for me, at least)
Two reasons:
It appends --profile xyz after up, which Docker Compose doesn't like (unknown flag: --profile).
Even if Compose wasn't erroring on up, Extra Args are only for the up command, and Compose also wants you to specify the profile as part of the down command.
COMPOSE_PROFILES seems to be a decent workaround
Since Compose takes anything from the Environment section of Komodo into its own environment, this can be used in lieu of command line args. It also sidesteps both of the Extra Args problems. Example:
COMPOSE_PROFILES=server
or for multiple profiles:
COMPOSE_PROFILES=server,db
@nano9g commented on GitHub (Jun 20, 2025):
I was just looking into this and would also appreciate native profile support. For anyone trying to get this to work in the meantime, here's what I discovered.
#### Extra Args didn't work (for me, at least)
Two reasons:
1. It appends `--profile xyz` after `up`, which Docker Compose doesn't like (`unknown flag: --profile`).
2. Even if Compose wasn't erroring on `up`, Extra Args are only for the `up` command, and Compose also wants you to specify the profile as part of the `down` command.
#### `COMPOSE_PROFILES` seems to be a decent workaround
Since Compose takes anything from the **Environment** section of Komodo into its own environment, this can be used in lieu of command line args. It also sidesteps both of the Extra Args problems. Example:
```
COMPOSE_PROFILES=server
```
or for multiple profiles:
```
COMPOSE_PROFILES=server,db
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @cyndane31 on GitHub (Jun 17, 2025).
I currently use compose service profiles to control the webui's for a few different backend services, namely my various databases. As far as I can tell, the only way to control deployment of a specific profile is using Extra Args to specify --profile=xxx. A UI element to control the deployed profile near the rest of the control elements would be a nice small QoL improvement.
@nano9g commented on GitHub (Jun 20, 2025):
I was just looking into this and would also appreciate native profile support. For anyone trying to get this to work in the meantime, here's what I discovered.
Extra Args didn't work (for me, at least)
Two reasons:
--profile xyzafterup, which Docker Compose doesn't like (unknown flag: --profile).up, Extra Args are only for theupcommand, and Compose also wants you to specify the profile as part of thedowncommand.COMPOSE_PROFILESseems to be a decent workaroundSince Compose takes anything from the Environment section of Komodo into its own environment, this can be used in lieu of command line args. It also sidesteps both of the Extra Args problems. Example:
or for multiple profiles: