mirror of
https://github.com/moghtech/komodo.git
synced 2025-12-05 19:17:36 -06:00
[PR #740] [MERGED] 1.19.1 #770
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/moghtech/komodo/pull/740
Author: @mbecker20
Created: 8/18/2025
Status: ✅ Merged
Merged: 8/24/2025
Merged by: @mbecker20
Base:
main← Head:1.19.1📝 Commits (10+)
bcbe75cstart 1.19.10c30229deploy 1.19.1-dev-1b7dab13Global Auto Update rustdoc6ee7a29support stack additional files420c9c0deploy 1.19.1-dev-24fe84c1Fe support additional file language detection8b1a323fix tsc5bbd551Fix: Example code blocks got interpreted as rust code, leading to compilation errors (#743)38857cbEnhanced Server Stats Dashboard with Performance Optimizations (#746)829e8f3gen types📊 Changes
99 files changed (+4637 additions, -1674 deletions)
View changed files
📝
Cargo.lock(+241 -231)📝
Cargo.toml(+10 -9)📝
bin/cli/src/command/container.rs(+1 -1)📝
bin/cli/src/command/execute.rs(+14 -0)📝
bin/cli/src/command/list.rs(+1 -1)📝
bin/cli/src/command/mod.rs(+1 -1)📝
bin/core/src/alert/discord.rs(+32 -0)📝
bin/core/src/alert/mod.rs(+239 -3)📝
bin/core/src/alert/ntfy.rs(+1 -199)📝
bin/core/src/alert/pushover.rs(+1 -199)📝
bin/core/src/alert/slack.rs(+35 -0)📝
bin/core/src/api/execute/alerter.rs(+79 -3)📝
bin/core/src/api/execute/build.rs(+47 -29)📝
bin/core/src/api/execute/deployment.rs(+31 -14)📝
bin/core/src/api/execute/mod.rs(+13 -2)📝
bin/core/src/api/execute/stack.rs(+456 -37)📝
bin/core/src/api/read/server.rs(+13 -1)📝
bin/core/src/api/write/stack.rs(+9 -1)📝
bin/core/src/helpers/procedure.rs(+34 -0)📝
bin/core/src/helpers/update.rs(+10 -0)...and 79 more files
📄 Description
Changelog
🚨 In order to use
config_files, Periphery should also be updated to v1.19.1❗️In addition to
ghcr.io, images are now also being published tomoghtech/komodo-*(Docker Hub)Stack
config_files🦎One of the most common requests was to allow in UI editing of
.envfiles on server / in repo. But really, there's not much difference between.envfiles and any config file which a Stack may be dependent on.This release adds the ability to configure all config files Stacks depend on, such as json / yaml app config files, and edit the files from the Komodo UI. Just add the relative path to the files (from the Run Directory) to the Stack "Config Files".
Users which are already using "Additional Env File" feature will find, with no change, that they can now see / edit all their additional env files from the UI. The only difference is that "Additional Env Files" will also be included in the
docker compose upcommand (with --env-file flag), while "Config Files" will not.The UI editors support syntax highlighting for a couple of common formats, such as toml, yaml, json, ini, and shell / .env. It will be challenging to add support for all the various formats used, so I won't personally accept requests to add more. The support is set up for extension though, please raise a PR adding support for additional syntax highlighting you would like and I am happy to review and merge it.
Deploy Stack If Changed 🦎
The biggest issue with Deploy Stack If Changed up to v1.19.1 was that it would only Redeploy if one of the compose files changed. If the commit is only to config file, these changes would be missed.
Now in v1.19.1, "Config Files" and "Additional Env Files" will also be tracked and diffed for changes. This means changes made only to a config / additional env file can also trigger deploy using Deploy Stack If Changed.
Any change made to a compose file or additional env file will always lead to a full Redeploy. However users are able to configure what kind of behavior diffs to config files leads to, either globally for the Stack or at the service level. For example, you can set diffs in a config file to only restart a specific service or services.
Action Example 🦎
If you configure Stacks with all dependent
additional_files, you can create an Action like this:It is re-usable in multiple Procedures, which can wrap the Action an hardcode the actual Repo.
You then setup webhooks for the Procedure on push, or can schedule the Procedure to run at polling intervals.
Community Contributions 🦎
This last week saw a ton of end-to-end feature development in community contributions, and I wanted to highlight them here:
executeAPI -- RunStackService -- in #732 by @bpbradleydocker compose runResource
moghtech/komodo-*(docker.io)Misc
executeAPI -- SendAlert🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.