I have stacks with multiple services where often only some of them need certain vars. I usually have several files for this like:
.grafana.env
.opnsense-exporter.env
.alertbot-matrix.env
They contain secrets and e.g. grafana doesn't need to know opnsense API keys but the exporter does.
I can manually copy them into the repo once it's created, but now I am using Komodo var management for stacks with only a single .env file and the workaround for those with multiples. It would be straightforward to have multiple "Environment" sections to assign variables to certain containers only.
Originally created by @tofuwabohu on GitHub (Nov 7, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/967
I have stacks with multiple services where often only some of them need certain vars. I usually have several files for this like:
- .grafana.env
- .opnsense-exporter.env
- .alertbot-matrix.env
They contain secrets and e.g. grafana doesn't need to know opnsense API keys but the exporter does.
I can manually copy them into the repo once it's created, but now I am using Komodo var management for stacks with only a single .env file and the workaround for those with multiples. It would be straightforward to have multiple "Environment" sections to assign variables to certain containers only.
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 @tofuwabohu on GitHub (Nov 7, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/967
I have stacks with multiple services where often only some of them need certain vars. I usually have several files for this like:
They contain secrets and e.g. grafana doesn't need to know opnsense API keys but the exporter does.
I can manually copy them into the repo once it's created, but now I am using Komodo var management for stacks with only a single .env file and the workaround for those with multiples. It would be straightforward to have multiple "Environment" sections to assign variables to certain containers only.