There should be support for some files that are outside a GitHub repository in a Git Repo stack. Some use cases include certificate files, secret files, and configs, which may contain private contents. There could also be server-specific configurations, and this would allow one GitHub repository to be used for multiple projects across servers.
Originally created by @6ixfalls on GitHub (Sep 7, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/820
There should be support for some files that are outside a GitHub repository in a Git Repo stack. Some use cases include certificate files, secret files, and configs, which may contain private contents. There could also be server-specific configurations, and this would allow one GitHub repository to be used for multiple projects across servers.
Discussion:
https://github.com/moghtech/komodo/discussions/811#discussioncomment-14329312
I'd love to see the same thing for "UI Defined" stacks. Some stacks require another config file or a second env file, which currently can't be managed form within Komodo. This would put it on parity with the "Files on Server" functionality already implemented.
<!-- gh-comment-id:3276298580 -->
@trexwe commented on GitHub (Sep 10, 2025):
I'd love to see the same thing for "UI Defined" stacks. Some stacks require another config file or a second env file, which currently can't be managed form within Komodo. This would put it on parity with the "Files on Server" functionality already implemented.
Weird about the distinction between Files on Server and UI Defined - I presume those could be merged into one along with this feature (since UI Defined stacks don't have config files for some reason).
<!-- gh-comment-id:3289020885 -->
@6ixfalls commented on GitHub (Sep 14, 2025):
Weird about the distinction between Files on Server and UI Defined - I presume those could be merged into one along with this feature (since UI Defined stacks don't have config files for some reason).
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 @6ixfalls on GitHub (Sep 7, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/820
There should be support for some files that are outside a GitHub repository in a Git Repo stack. Some use cases include certificate files, secret files, and configs, which may contain private contents. There could also be server-specific configurations, and this would allow one GitHub repository to be used for multiple projects across servers.
Discussion:
https://github.com/moghtech/komodo/discussions/811#discussioncomment-14329312
@trexwe commented on GitHub (Sep 10, 2025):
I'd love to see the same thing for "UI Defined" stacks. Some stacks require another config file or a second env file, which currently can't be managed form within Komodo. This would put it on parity with the "Files on Server" functionality already implemented.
@6ixfalls commented on GitHub (Sep 14, 2025):
Weird about the distinction between Files on Server and UI Defined - I presume those could be merged into one along with this feature (since UI Defined stacks don't have config files for some reason).