DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to add a plugin lifecycle to a Rust application with Rutis

Run plugins in a Rust program that starts once dependencies are ready and cleans up on stop.

Who it is forA Rust developer building a long-running program that must swap providers and release resources without leaking them.

The problemHand-managing startup order, rollback and cleanup for swappable components is error-prone when components are replaced repeatedly.

The outcomeA Rust program in which a dependent plugin starts when its service appears, restarts when the provider is replaced, and releases everything exactly once.

What you need first

  • Node.js with npm, or Bun, for the TypeScript path
  • uv for the Python path
  • Go for the Go path
  • A Rust toolchain with cargo for the embedding path

Steps

  1. Run cargo add rutis and cargo add tokio --features full in your Rust project.
  2. Define a plugin that provides a service and another plugin that depends on it, as shown in the README quick start.
  3. Run cargo run -p rutis --example quickstart from a clone of the repository to see the lifecycle in action.

Prompt for your agent

Using the repo arcships/rutis, add the rutis and tokio crates to <target> with `cargo add rutis` and `cargo add tokio --features full`, then run `cargo run -p rutis --example quickstart` from a clone. Expected output: the listener printing a greeting, then printing a new greeting after the provider is replaced. Verify that the listener restarts without any change to its own code.

Caveat. The README describes the Rust API as the core, so expect to read the docs at docs.rs/rutis for the full set of calls beyond the example.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page