Rekindle runs the Cargo build and development lifecycle from Mix. Cargo remains the source of truth for Rust dependencies and incremental compilation.
Prepare tools
Prepare every enabled target:
mix rekindle.setup
Limit setup to one target when necessary:
mix rekindle.setup web
mix rekindle.setup desktop
For Web builds, Rekindle installs the pinned wasm-bindgen-cli release into a
versioned user cache. A global installation is not required.
Check the project
Run the read-only diagnostic task:
mix rekindle.doctor
It checks the Rekindle configuration, Cargo metadata, target support, selected integration, and pinned Web tooling.
Start development
Start Phoenix and the Rekindle development services together:
mix rekindle.dev
Arguments are passed through to mix phx.server.
Files below client/ are watched and rebuilt through Cargo. A successful Web
build publishes an immutable development generation and notifies connected
browsers. For a desktop replacement, Rekindle stops the current process before
starting the candidate and selects the candidate only after it remains running
through the readiness interval. If the candidate fails and a retained
executable exists, Rekindle makes one best-effort restart of that executable;
the restart can also fail. A failed first launch has no previous executable to
restore.
Rekindle's supervised development services run only when the Phoenix endpoint has code reloading enabled.
Build explicitly
Build an enabled target without starting its development runtime:
mix rekindle.build web
mix rekindle.build desktop
Development artifacts and state are stored below .rekindle/dev.