Skip to content

Docs: schema management options for message storage, linked to Weasel and the stateful resource model - #5437

Merged
jeremydmiller merged 1 commit into
mainfrom
docs-schema-management-links
Nov 7, 2026
Merged

jeremydmiller merged 1 commit into
mainfrom
docs-schema-management-links

Conversation

@jeremydmiller

Copy link
Copy Markdown
Member

What

Documentation only. Wherever the Wolverine docs touch database schema management for message storage, link to the Weasel reference and to the JasperFx stateful resource model, and explain the options.

  • docs/guide/durability/managing.md: the stateful resource link now goes to the shared-libs docs; a new Choosing an Approach section (startup by default via AutoBuildMessageStorageOnStartup / UseResourceSetupOnStartup(), resources setup or db-apply as a deployment step, db-patch / db-dump for a DBA, db-assert / resources check as the gate); ResourceMigrationFailureMode links to its JasperFx reference; the disable-migration tip links the explicit applies and adds the CritterStackDefaults one-liner, since AutoBuildMessageStorageOnStartup defaults from the JasperFx profile's ResourceAutoCreate (checked in WolverineOptions.cs); the startup and resources setup sections link the resource model.
  • docs/guide/command-line.md: the intro no longer says Oakton; the Other Highlights list now describes resources, the Weasel db-* commands and check-env with links.
  • docs/guide/durability/{postgresql,sqlserver,sqlite,mysql,oracle}.md: the "apply the Wolverine resource migration before starting" sentence for the ordering opt-in now says how (resources setup / db-apply) and links the options section.
  • docs/guide/durability/{marten,polecat}/index.md: the inbox/outbox registration bullets say the tables ride db-apply, db-patch and resources setup with the store's schema; the Polecat one gains the link its Marten twin already had.
  • docs/guide/durability/efcore/migrations.md and docs/guide/durability/index.md: link the options section and the db-* commands for managed DbContext types.

All external links were checked live. No snippets changed.

Part of a sweep across Marten, Polecat, Fisher, Wolverine, CritterWatch and Weasel itself (the Weasel docs PR adds a canonical "Choosing a Schema Management Approach" page these pages can link to once redeployed).

🤖 Generated with Claude Code

…asel and the stateful resource model

Managing Message Storage gains a "Choosing an Approach" table (startup by default, resources setup
or db-apply as a deployment step, db-patch / db-dump scripts, db-assert as the gate), says that the
envelope, node, transport and EF Core tables are Weasel schema objects, links the stateful resource
model to shared-libs.jasperfx.net instead of GitHub, links ResourceMigrationFailureMode and
CritterStackDefaults, and explains that AutoBuildMessageStorageOnStartup takes its default from the
JasperFx profile.

The command line page drops the Oakton wording and lists resources, the db-* commands and check-env
with their references. The five database storage pages say how to apply the queue migration under
AutoCreate.None; the Marten, Polecat and EF Core integration pages say their tables ride the same
commands.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@jeremydmiller
jeremydmiller merged commit 8e2f713 into main Nov 7, 2026
This was referenced Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant