Soenneker.Flywheel.Redis 5.0.33

Soenneker.Flywheel.Suite

Background jobs, Redis storage, source generators, and a live Blazor dashboard in one solution.

Background work. Everything in view.

Queue a typed job, coordinate workers across instances, and follow each execution in the live Blazor dashboard.

The optional Flywheel Dashboard, shown with illustrative demo data.

Explore Flywheel · Dashboard · Run the demo

Packages

Each project produces its own NuGet package. The suite is the repository and solution, not a combined runtime package.

Dashboard does not bring Redis or the server runtime into WebAssembly. Projects reference each other directly in this solution; NuGet packing converts those references into separate package dependencies.

Run once for the current application version

From the hosting application, submit a registered job through IJobClient:

await jobs.EnqueueForCurrentVersion(job, payload);

Flywheel automatically identifies the hosting application build and creates one shared job per job name and build within the Redis namespace. Only engines running that exact build can claim it, so older application instances in warmup slots skip the job. The submission marker survives completed-job cleanup; normal retries and lease recovery still apply, so handlers must be idempotent.

See version-specific jobs for build identity overrides and execution semantics.

One demo

Install .NET 10 and run Redis 6.0.9 or newer on localhost:6379, then:

dotnet dev-certs https --trust
dotnet run --project test/Soenneker.Flywheel.Demo

In a second terminal, run dotnet run --project test/Soenneker.Flywheel.Dashboard.Demo. Open https://localhost:7039/ and sign in with admin / flywheel-demo in Development. The engine/API runs at https://localhost:7443/ and the dashboard runs separately. The solution's Demo startup configuration starts both and opens only the dashboard browser. Stop both with Ctrl+C. See demo configuration.

Development

dotnet build Soenneker.Flywheel.Suite.slnx
dotnet test --project test/Soenneker.Flywheel.Dashboard.Tests

Redis integration tests use FLYWHEEL_TEST_REDIS, defaulting to localhost:6379. Manual Redis benchmarks live in the Redis test project and are excluded from normal test runs. The product website is included under src/Soenneker.Flywheel.Website. Its separate website workflow exports and deploys the static site to Cloudflare; see website development and deployment.

Dashboard pages use Lepton lifecycle management. A typed consumer handles API calls through the Flywheel API client, while a shared live client owns SignalR connections and subscriptions. Shared communication contracts keep the server and dashboard aligned. HomePath controls dashboard navigation; EnginePath independently controls API, authentication, and SignalR routes and must match on the backend and client. Either prefix can be / or a custom path. See prefix configuration.

Releases

JSON contracts use explicit camelCase property names and Soenneker.Utils.Json. See JSON storage contracts.

build-and-test.yml builds the entire solution, runs the four test projects with Redis, publishes the hosted demo, and packs five separate packages. publish-package.yml calls that validation workflow and then runs a deployment matrix with one job per package, publishing to NuGet and GitHub Packages. A GitHub release is created only after every deployment succeeds.

All packages share 5.0.<publish workflow run number>. Local builds default to 5.0.0; BUILD_VERSION overrides it. The 5.0 series avoids collisions with independently versioned 4.0 releases and reflects the move of shared job and dashboard contracts into Soenneker.Flywheel.Communication. Update imports for DTOs, enums, requests, responses, and log DTOs from Soenneker.Flywheel.Core to Soenneker.Flywheel.Communication. The storage server snapshot is now Communication.Responses.WorkerServerView; the dashboard response remains Communication.Responses.ServerView.

Documentation

• Core
• Redis
• Generators
• Dashboard and authentication