Add LavinMQ hosting integration documentation - supersedes PR #2634 #4303
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds comprehensive documentation for the LavinMQ hosting integration in the .NET Aspire Community Toolkit, superseding PR #2634 with all review feedback addressed.
Overview
LavinMQ is a wire-compatible messaging broker alternative to RabbitMQ built on Crystal. This integration enables developers to easily host LavinMQ containers in .NET Aspire applications while leveraging existing RabbitMQ client libraries for seamless compatibility.
Changes Made
New Documentation
docs/community-toolkit/hosting-lavinmq.md
- Complete integration guide covering:Updated Files
docs/community-toolkit/overview.md
- Added LavinMQ to the hosting integrations listdocs/toc.yml
- Added table of contents entry for LavinMQ documentationFixes Applied from PR #2634 Review
All feedback from the original PR has been addressed:
LavinMQ
tolavinMq
for camelCase conventionDocumentation Highlights
The documentation demonstrates how LavinMQ's wire compatibility with RabbitMQ allows developers to:
This integration provides a lightweight alternative to RabbitMQ while maintaining full API compatibility, making it easy for teams to switch between message brokers without code changes.
Validation
Closes #2634 (supersedes)
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.
Internal previews