[GH-ISSUE #92] Deployment / Stack can manage config files in UI, and write them just before deploy time for mounting to containers #3091

New Issue

GiteaMirror · 2026-04-13T14:43:47-05:00

GiteaMirror commented

2026-04-13 14:43:47 -05:00

Originally created by @mbecker20 on GitHub (Sep 25, 2024).
Original GitHub issue: https://github.com/moghtech/komodo/issues/92

With a better UI editor for config files, this will be nice.

(Deployment | Stack).config_file: Array<{ path: string; content: string; }>

The Example Resource Toml:

[[deployment]]
name = "example"
config.image.type = "Image"
config.image.params.image = "caddy"
config.network = "host"
config.volumes = "/configs/example/Caddyfile:/etc/caddy/Caddyfile"
[[deployment.config_file]]
path = "/configs/example/Caddyfile"
content = """
site.domain {
   reverse_proxy localhost:9120
}
"""
[[deployment.config_file]]
path = "/configs/example/another"
content = """
# You don't need anything in here,
# just demonstrating that you can define multiple config files.
"""

[[stack]]
name = "example"
stack.file_contents = """
services:
  caddy:
    image: caddy
    volumes:
      - /configs/example/Caddyfile:/etc/caddy/Caddyfile
"""
[[stack.config_file]]
path = "/configs/example/Caddyfile"
content = """
site.domain {
   reverse_proxy localhost:9120
}
"""

Originally created by @mbecker20 on GitHub (Sep 25, 2024). Original GitHub issue: https://github.com/moghtech/komodo/issues/92 With a better UI editor for config files, this will be nice. `(Deployment | Stack).config_file: Array<{ path: string; content: string; }>` The Example Resource Toml: ```toml [[deployment]] name = "example" config.image.type = "Image" config.image.params.image = "caddy" config.network = "host" config.volumes = "/configs/example/Caddyfile:/etc/caddy/Caddyfile" [[deployment.config_file]] path = "/configs/example/Caddyfile" content = """ site.domain { reverse_proxy localhost:9120 } """ [[deployment.config_file]] path = "/configs/example/another" content = """ # You don't need anything in here, # just demonstrating that you can define multiple config files. """ [[stack]] name = "example" stack.file_contents = """ services: caddy: image: caddy volumes: - /configs/example/Caddyfile:/etc/caddy/Caddyfile """ [[stack.config_file]] path = "/configs/example/Caddyfile" content = """ site.domain { reverse_proxy localhost:9120 } """ ```

GiteaMirror added the enhancement label 2026-04-13 14:43:47 -05:00

GiteaMirror commented

2026-04-13 14:43:49 -05:00

@NeurekaSoftware commented on GitHub (Jun 2, 2025):

This would be amazing!

@NeurekaSoftware commented on GitHub (Jun 2, 2025): This would be *amazing*!

GiteaMirror commented

2026-04-13 14:43:50 -05:00

@samumatic commented on GitHub (Jun 5, 2025):

It would be great if the config files were not only saved in the komodo interface, but could also be saved in one or the same git repo, just like the docker compose files - for versioning.
So less like another field in the style of ENV variables, but more like a new section in the “Info” tab.

@samumatic commented on GitHub (Jun 5, 2025): It would be great if the config files were not only saved in the komodo interface, but could also be saved in one or the same git repo, just like the docker compose files - for versioning. So less like another field in the style of ENV variables, but more like a new section in the “Info” tab.

GiteaMirror commented

2026-04-13 14:43:51 -05:00

@TheLinuxGuy commented on GitHub (Jul 14, 2025):

this would be great! I have several stacks that have some text files (json, yaml) that i would love to be able to leverage Komodo web UI to modify them and easily restart the containers in the stack after changes are made.

@TheLinuxGuy commented on GitHub (Jul 14, 2025): this would be great! I have several stacks that have some text files (json, yaml) that i would love to be able to leverage Komodo web UI to modify them and easily restart the containers in the stack after changes are made.

GiteaMirror commented

2026-04-13 14:43:51 -05:00

@joshualyon7 commented on GitHub (Jul 15, 2025):

+1 for this - I use the secrets & variables features heavily with my environment management with stacks and would love the same type of configuration for services that don't play nice with configuration via environment variables. I also use the remote repo method of pulling compose files and would rather not store my config files that contain secrets in a remote git repo

@joshualyon7 commented on GitHub (Jul 15, 2025): +1 for this - I use the secrets & variables features heavily with my environment management with stacks and would love the same type of configuration for services that don't play nice with configuration via environment variables. I also use the remote repo method of pulling compose files and would rather not store my config files that contain secrets in a remote git repo

GiteaMirror commented

2026-04-13 14:43:52 -05:00

@mbecker20 commented on GitHub (Aug 24, 2025):

It would be great if the config files were not only saved in the komodo interface, but could also be saved in one or the same git repo, just like the docker compose files - for versioning. So less like another field in the style of ENV variables, but more like a new section in the “Info” tab.

https://github.com/moghtech/komodo/releases/tag/v1.19.1

@mbecker20 commented on GitHub (Aug 24, 2025): > It would be great if the config files were not only saved in the komodo interface, but could also be saved in one or the same git repo, just like the docker compose files - for versioning. So less like another field in the style of ENV variables, but more like a new section in the “Info” tab. https://github.com/moghtech/komodo/releases/tag/v1.19.1

GiteaMirror commented

2026-04-13 14:43:55 -05:00

@NeurekaSoftware commented on GitHub (Sep 10, 2025):

@mbecker20 I was excited to finally use Komodo now that managing config files was added in 1.19.1, but I see that the option doesn't exist for UI Defined. I prefer not to keep secrets in a git repo and files on disk doesn't appeal to me as that's the entire point if using Komodo for my use case.

I like to be able to manage everything from the UI and easily create templates that I can share with my friends.

Do you have any plans to make both the creation and management of config files available for UI Defined?

edit: created issue #870

@NeurekaSoftware commented on GitHub (Sep 10, 2025): @mbecker20 I was excited to finally use Komodo now that managing config files was added in 1.19.1, but I see that the option doesn't exist for `UI Defined`. I prefer not to keep secrets in a git repo and files on disk doesn't appeal to me as that's the entire point if using Komodo for my use case. I like to be able to manage everything from the UI and easily create templates that I can share with my friends. Do you have any plans to make both the creation and management of config files available for `UI Defined`? edit: created issue #870

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#3091