Releases: mbecker20/komodo
v1.13.4 Komodo
Hey guys,
This patch fixes a bug preventing users from using private image registries with stack deploys. Thanks to @febalist for catching this.
Docs: https://docs.monitor.dev | Demo: https://demo.monitor.dev
Contributors
Assets 4
v1.13.3 Komodo
Last patch for 1.13
- Improve periphery disk mount filtering. If needed, pass Periphery a whitelist / blacklist of the disks (by mount path) to include in the disk report
- See example
Now its off to 1.14.
Docs: https://docs.monitor.dev/ | Demo: https://demo.monitor.dev/
Enjoy 🦎
v1.13.2 Komodo
Hey guys, another patch to Komodo 🦎
-
Users can now manage compose files themselves on their hosts. Just configure the Stack to point to the file/s on your machine, and you are good to go. Users which already have stacks deployed using compose files on the host can very easily adopt Monitor to manage their existing Stacks.
-
Dockerized Periphery - I now provide a docker image for periphery: https://github.com/mbecker20/monitor/pkgs/container/periphery
- See https://docs.monitor.dev/docs/connecting-servers#install-the-periphery-agent---container for an example compose file.
-
All In One compose file: Deploy Monitor Core and Periphery with a single command: https://github.com/mbecker20/monitor/blob/main/config_example/aio.compose.yaml
-
Monitor Builds can now disable auto incrementing the patch version on every build. Users can now fully manage the image versions they produce.
Docs: https://docs.monitor.dev/ | Demo: https://demo.monitor.dev/
Enjoy 🦎
v1.13.1 Komodo
Hey guys, just a small patch to Komodo 🦎
- Fixed some edge cases I noticed deploying more compose files
- Improved frontend responsiveness on phone / tablet etc.
- Finished "Repo build" feature, I use it to:
-- spawn an Aws instance
-- clone Monitor repo, build binary, push it to Gitea generic packages.
To update, just compose down-compose up Core, update periphery using the installer. Api is backward compatible so it doesn't matter the ordering you update.
Docs: https://docs.monitor.dev | Demo: https://demo.monitor.dev
Enjoy 🦎
v1.13 - Komodo - Docker compose support
🦎 Monitor v1.13 - Komodo 🦎
This is a big release, so we are giving it a name. The Komodo Dragon is a sub-species of Monitor lizard, and is the largest living lizard in the world.
Note. With this release move to https://docs.monitor.dev. The official docker image for Monitor Core also moves to gchr.io/mbecker20/monitor:latest. Those running Core on Arm can use the ghcr.io/mbecker20/monitor:latest-aarch64 series of tags.
Also, I'm hosting a demo now. Try redeploying an Immich stack or a Jellyfin stack using Monitor yourself. Any username / password will do. https://demo.monitor.dev.
Whats new:
-
Deploy docker compose files using the new 'Stack' resource. You can paste a file directly into the UI, or you can push the files to a git repo and have the Stack deploy from there. You can also setup webhooks to automatically re/deploy the stack whenever you push a change to the repo.
-
Builds can now push the image to a configurable image repository name. They can also attach a custom tag after the version, achieving parallel tagging in a single image repo for different release channels.
-
Repos can now be "built" using single-use AWS instance. The idea is that you can have some code and a script to build the code and ship the binary off yourself. But users have to handle their own versioning of the binaries with this method.
-
Simplified the core setup procedure by providing a docker compose file here: https://github.com/mbecker20/monitor/blob/main/config_example/core.compose.yaml
-
Add / manage providers in the UI. Both git providers, and registry providers. They can still be managed in the config file if that is preferred, but with this change there is no more need to create a config file on your host. See the example compose file above .
-
Arm64 support included in the releases for Core and Periphery. The periphery installer can detect which binary should be loaded.
- Users running Monitor Core on Arm, take note of the image for you to use above.
-
More inline hints. These guide new users through using Monitor, and have been added throughout the UI.
-
Page layout / styling improvements courtesy of @karamvirsingh98
Updating
Just switch the core image to ghcr.io/mbecker20/monitor and redeploy. It can be upgraded in place.
To upgrade periphery agents, just run the periphery installer again on your hosts. link. You can upgrade Core / periphery in any order, as they are backward compatible with eachother.
🦎 Hope you guys enjoy 🦎
Contributors
Assets 4
v1.12.0
Expands git provider / docker registry support to all providers, including self hosted ones such as Gitea (tested for private repo clone, repo webhook delivery, and docker image push).
WARNING 🚨 Breaking changes
Some changes in this release are breaking with previous versions.
Users upgrading from 1.11 or earlier must update their core and periphery configuration files docker_account and github_account declarations to the new format. This also allows for configuration of custom git provider domains, such as self hosted ones. Additionally, organizations are now configured per docker registry provider, so the fields github_organizations and docker_organizations have been removed. The field github_webhook_secret has been renamed to just webhook_secret, and the field github_webhook_base_url has been renamed to webhook_base_url.
Users must also run the database migration for the Core version they are upgrading from.
Additionally, image build, repo clone, and container deploy will not work with older periphery versions, so periphery binaries must be updated on connected servers to restore this functionality. Other periphery functions (like stopping containers, system stats, etc) remain backward compatible.
v1.11.0
Configure base permissions on all resources of a specific type (Read on all servers, Execute on all builds, etc.).
- Supported for both users and user groups
UserGroup permissions declared in ResourceSync can now use regex to match against many resources.
See https://docs.monitor.mogh.tech/docs/sync-resources#user-group for example.