clemcer/LoggiFly v2.0.0 on GitHub

Caution

v2 contains breaking changes. Your v1 config will not work without migration. Run the migration script and read the migration guide before upgrading.

v2 is a major redesign of LoggiFly's configuration system. The rigid per-container config blocks are replaced by a flexible rules-based system with glob pattern matching. Along with the new architecture come renamed fields, removed settings, changed defaults and a cleaner inheritance model for settings.

Due to the scope of this rewrite, these notes cover highlights only. For all details, see the migration guide and the updated docs.

You can find a side by side comparison of v1 vs v2 configs here and for a complete overview of the new config structure refer to the annotated config reference.

Migration script (reads /config/config.yaml, writes /config/configv2.yaml):

docker run --rm \
  -v /path/to/your/config/dir:/config \
  ghcr.io/clemcer/loggifly-migrate:v1-to-v2

After running it, check the log output for warnings, then work through the migration guide to review the behavioral changes that require your judgment.

Full Migration Guide

What's now possible in v2

Flexible rule-based targeting: rules replace the old per-container dict. Match containers by glob pattern (web-*, *-db, *), combine multiple include and exclude patterns per rule, and let one rule cover dozens of containers at once. (docs)
Rule groups for shared settings: use groups to apply shared settings like scope, defaults, or keywords to a set of rules without repeating them on every rule (docs)
New threshold-based triggering (trigger_on): a trigger can now require N matches within a time window before firing. Applies to both log keyword matches and container events. (docs)
Jinja2 templates: title_template and message_template now use Jinja2 syntax ({{ variable }} instead of {variable}), unlocking filters, conditionals, and more. The migration script handles this conversion automatically (docs).

Bug fixes

Olivetin Integration requiring a password even when it is not necessary (#78)
Monitoring stops when LoggiFly restarts a container (#79)

Other

updated docs and added migration guide
added ko-fi support link. If you find LoggiFly useful, consider supporting it

Chores

chore(deps): bump apprise from 1.9.7 to 1.10.0 by @dependabot[bot] in #94
chore(deps): bump pydantic from 2.12.5 to 2.13.3 by @dependabot[bot] in #93
chore(deps-dev): bump vitepress from 1.6.3 to 1.6.4 by @dependabot[bot] in #92

Full Changelog: v1.8.0...v2.0.0