Download the PHP package pushinbr/laravel-rabbit without Composer

Laravel Rabbit

RabbitMQ library for Laravel with a native queue driver, AMQP 0-9-1 publishing and consuming, topology declarations, TLS, publisher confirms, QoS, host failover, RabbitMQ Management HTTP API support, and security validation.

[!IMPORTANT] The package registers a Laravel queue driver named rabbitmq. When QUEUE_CONNECTION=rabbitmq, Laravel's native dispatch(), onQueue(), delay(), queue:work, retries, backoff, failed jobs, batches, chained jobs, and unique jobs continue to work through the standard Laravel worker flow.

Table of Contents

• Compatibility
• Feature Overview
• Installation
• Quick Start
• Laravel Queue Driver
• Delayed Jobs
• RabbitMQ Management API
• Artisan Commands
• Low-Level AMQP Usage
• Topology
• Production Options
• Security
• Testing

Compatibility

Feature Overview

Installation

Install the package:

Publish the configuration file:

Or use the installer command:

Laravel auto-discovery registers:

Quick Start

1. Configure RabbitMQ

[!TIP] Leave RABBITMQ_QUEUE_ROUTING_KEY unset for most Laravel apps. The package will use the queue name from onQueue() as the routing key.

Optional payload signing for the queue driver:

[!IMPORTANT] Payload signing protects the Laravel worker from unsigned or tampered queue messages. Enable it only after all producers that publish Laravel jobs through RabbitMQ use the same signing key, because unsigned existing messages will be rejected when verification is enabled.

2. Dispatch a Job

3. Run the Worker

Because QUEUE_CONNECTION=rabbitmq, the command above uses RabbitMQ without passing the connection name. This also works:

4. Check the Setup

Laravel Queue Driver

The laravel_queue config section is merged automatically into queue.connections.rabbitmq.

Laravel Support Matrix

Worker Examples

Job Example

Delayed Jobs

Default strategy:

Delayed message exchange strategy:

RabbitMQ Management API

The Management API integration is optional. The queue driver can dispatch and consume jobs without it. Enable it when you want broker-level metrics and operational visibility.

Management Configuration

Metrics Mapping

[!NOTE] delayedSize() is accurate for this package's default TTL delay queues. RabbitMQ does not expose queued messages inside an x-delayed-message exchange as normal queue depth.

Management Client Usage

Call any Management API endpoint directly:

Use non-GET endpoints through request():

Artisan Commands

Laravel's native queue commands remain the primary interface.

The package also adds RabbitMQ-specific operational commands.

rabbitmq:doctor

Checks:

• connection configuration exists
• security policy passes
• QUEUE_CONNECTION is rabbitmq
• Laravel queue driver is registered
• AMQP channel can open
• Management API is reachable when enabled
• optional publish/consume round trip succeeds

rabbitmq:management

rabbitmq:stats

When the Management API is enabled, this command shows real broker metrics. Without it, RabbitMQ's AMQP queue declaration only provides total ready depth, so reserved and delayed counts are not available.

Other Commands

Low-Level AMQP Usage

Use the facade when you need direct AMQP behavior outside Laravel's queue worker.

Publish Text

Publish JSON

Consume Messages

By default, a message is acknowledged when the callback finishes without errors. If the callback returns false, the message is nacked.

Consume Options

Get One Message

Use a Specific Connection

Facade shortcut:

Topology

The package can automatically declare exchanges, queues, and bindings when a channel is opened.

Manual declarations are also supported:

Production Options

Publisher Confirms

Publisher confirms are enabled by default.

To handle returned messages, publish with mandatory=true and register a return listener.

QoS / Prefetch

Host Failover

Security

Queue Payload Signing

Queue payload signing is an optional defense against job injection. When enabled, the driver adds an HMAC signature to every Laravel queue payload it publishes. During queue:work, messages without a valid signature are rejected before Laravel attempts to execute the job.

[!NOTE] Payload signing does not replace broker security. Keep RabbitMQ credentials scoped per app, restrict vhost permissions, use TLS outside local development, and do not allow untrusted systems to publish into Laravel worker queues.

TLS

For security, verify_peer=false or verify_peer_name=false throws an exception unless security.allow_insecure_tls=true.

Security Guards

Recommendations:

• Use TLS outside local development.
• Do not use the guest user on remote hosts.
• Keep verify_peer and verify_peer_name enabled.
• Configure max_message_size when your application has a known payload limit.
• Prefer publisher confirms for important flows.

Message Properties

Accepted properties follow AMQPMessage.

Testing