1076111d3a
This PR contains the following updates: | Package | Update | Change | |---|---|---| | [docker.io/josh5/unmanic](https://redirect.github.com/Unmanic/unmanic) | minor | `b7a45c7` -> `3e29575` | Add the preset `:preserveSemverRanges` to your config if you don't want to pin your dependencies. --- ### Release Notes <details> <summary>Unmanic/unmanic (docker.io/josh5/unmanic)</summary> ### [`v0.3.0`](https://redirect.github.com/Unmanic/unmanic/releases/tag/0.3.0): [RELEASE] v0.3.0 [Compare Source](https://redirect.github.com/Unmanic/unmanic/compare/0.2.9...0.3.0) - \[NOTE] When upgrading to 0.3.0+, supporters will need to log in again. Thank you for your continued support.\ With this release comes support for remote logging and the Unmanic Central service. Unmanic Central is a self-hosted management and monitoring platform that lets you collect, store, and visualise logs and metrics from all your Unmanic installations in one place. **Key components:** - **Unmanic Central Datastore**\ A resilient, self-hosted store for Unmanic logs, metrics and data. - **Unmanic Central Frontend**\ A new web interface where you can build custom dashboards, configure real-time views, and drill down into every event and metric across your fleet. **What you can do with Unmanic Central:** - **Centralise log collection**\ Route logs (with automatic retry and buffering) from each Unmanic instance into one unified store. - **Monitor performance**\ Track library scan duration, service CPU/memory usage, plugin progress, file-processing changes (size, duration), and more—all correlated by installation. - **Visualise and alert**\ Create and share dashboards in the Central frontend to focus on metrics and events that matter, and integrate with Grafana for advanced querying and visualisation. - **Extend with Grafana**\ Optionally connect Grafana directly to your Central Datastore to build custom dashboards, set alerts, and leverage the full power of your data. **Availability:**\ Unmanic Central is a supporter-only feature. #### Service - \[NEW] Add initial log‐forwarding feature with on-disk buffering and remote endpoint support - Create remote‐log buffer with retention of 2 weeks to survive endpoint outages - Include installation name as a label in all remote logs - \[NEW] Introduce METRIC logs for library scan duration - \[NEW] Emit overall service resource-usage metrics (CPU, memory) as METRIC logs - \[NEW] Emit per-worker progress metrics (CPU%, memory%, elapsed time, progress%) as METRIC logs - \[NEW] Support a new “DATA” log type and send structured data to Unmanic Central - \[NEW] Add DATA logs for library scan metrics - \[FIX] Resolve supporter session & login issues introduced by recent API changes - \[FIX] Ensure logs generated before remote-logging is enabled are still captured and forwarded #### Plugin executor - \[NEW] Add “event runners” to emit lifecycle events at key task execution points - \[NEW] Introduce a shared, task-scoped data store for plugins via `TaskDataStore` - \[NEW] Enable spawning plugin work in isolated subprocesses with the new `PluginChildProcess` helper (live logs & progress) - \[IMPR] Enhance child-process cleanup with a global PID registry and guaranteed termination (including paused processes) - \[FIX] Ensure all plugin-spawned subprocesses are reliably terminated on service shutdown #### Docker - \[FIX] Correct the Docker development-environment run script #### Front-end - \[IMPR] Force immediate registration-status refresh after obtaining a new app token - \[FIX] Restore supporter-login flow following recent API changes - \[FIX] Allow sign-out when the remote API is unreachable </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4yMC4wIiwidXBkYXRlZEluVmVyIjoiNDEuMjAuMCIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6WyJhdXRvbWVyZ2UiLCJyZW5vdmF0ZS9jb250YWluZXIiLCJ0eXBlL21pbm9yIl19-->
title
| title |
|---|
| TrueCharts |
Community Helm Chart Catalog
TrueCharts is a catalog of highly optimised Helm Charts. Made for the community, By the community!
All our charts are supposed to work together and be easy to setup using any helm-compatible deployment tool, above all, give the average user more than enough options to tune things to their liking.
Getting started using TrueCharts
Support
Please check our FAQ, manual and Issue tracker There is a significant chance your issue has been reported before!
Still something not working as expected? Contact us! and we'll figure it out together!
Development
Our development process is fully distributed and agile, so every chart-maintainer is free to set their own roadmap and development speed and does not have to comply to a centralised roadmap. This ensures freedom and flexibility for everyone involved and makes sure you, the end user, always has the latest and greatest of every Chart installed.
Getting into creating Charts
For more information check the website: https://truecharts.org
Contact and Support
To contact the TrueCharts project:
-
Create an issue on Github issues
-
Open a Support Ticket
-
Send us an email
Contributors ✨
Thanks goes to these wonderful people (emoji key):
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?v=4?s=100)
![allcontributors[bot]](https://avatars.githubusercontent.com/in/23186?v=4?s=100)
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4?s=100)
This project follows the all-contributors specification. Contributions of any kind welcome!
Licence
Truecharts, is primarily based on a AGPL-v3 license, this ensures almost everyone can use and modify our charts. Licences can vary on a per-Chart basis. This can easily be seen by the presence of a "LICENSE" file in said folder.
An exception to this, has been made for every document inside folders labeled as docs or doc and their subfolders: those folders are not licensed under AGPL-v3 and are considered "all rights reserved". Said content can be modified and changes submitted per PR, in accordance to the github End User License Agreement.
SPDX-License-Identifier: AGPL-3.0
