mirror of
https://github.com/b0x207/miniflux-notifier.git
synced 2026-10-16 07:18:44 -07:00
Desktop notifications for Miniflux
- Rust 67.3%
- Nix 32.7%
The prior architecture relied upon the use of a `Vec<Entry>` which was rather flawed, including the fact that it was capped at 1000 results from the API endpoint. This also required more system resources to run than were really necessary. Instead, send the request with `&after=<timestamp>` to get just the entries since the last check. Waiting on the threads spawned for notification actions could also lead to stalls if the user ignores the notification rather than interacting with it (either opening or closing). Instead, a lightweight `tokio::spawn` can place it in the background where it will consume very little compute time. |
||
|---|---|---|
| src | ||
| .envrc | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| flake.lock | ||
| flake.nix | ||
| LICENSE | ||
| miniflux-notifier.service | ||
| README.md | ||
| treefmt.nix | ||
Miniflux Notifier
Get desktop notifications at select intervals about new, unread articles from a Miniflux server.
The program is a daemon for linux that can be run on a per-user basis.
Building
Make sure you have the rust toolchain installed (see rustup.rs).
cargo build --release
The build binary is a single file located at target/release/miniflux-notifier.
Running
The program should be run as a daemon and thus, it is up to you to determine how your system should start it. If you use Systemd, I would recommend using a user service.