Modules
Dust SDK — reactive global map client.
ETS-backed circular buffer for recent Dust operations.
Per-subscription worker process that receives events and calls the callback.
WebSocket client that connects to the Dust server via Phoenix Channels.
LiveDashboard page for Dust SDK introspection.
A single cached entry with metadata.
Reference to a file stored in Dust. Returned by Dust.get/2 when the value is a file.
The result of Dust.single_flight/4.
Macro that generates a named Dust facade module from application config.
A held lease — a snapshot capability handle returned by Dust.lease/3 and
Dust.renew/2.
A page of results from Dust.enum/3 or Dust.range/4.
Segment-aware glob matching against Dust.Protocol.Path segment
lists.
Segment-first paths for the Dust Elixir SDK.
Dotted-path helpers from the pre-segment-first capability version.
Bridges Dust events to Phoenix.PubSub.
Coordinated distributed cache-fill (a.k.a. single-flight) over a Dust lease.
Declarative callback handler for Dust store events.
One-off GenServer that starts last in the supervision tree and registers
all declared Dust.Subscriber modules with their respective SyncEngines.
Test helpers for applications that use Dust. In :manual test mode, Dust uses a memory cache and no server connection. Use these functions to control Dust state in tests.
Mix Tasks
Generates a migration that creates the dust_cache table.
Sets up Dust in your Phoenix application.