updated examples

Author: vyuldashev

src/examples/app.php

@@ -2,8 +2,8 @@
 
 return [
 
-	'providers' => [
+	'providers' => append_config([
 		'FintechFab\LaravelQueueRabbitMQ\LaravelQueueRabbitMQServiceProvider',
-	],
+	]),
 
 ];

src/examples/queue.php

@@ -1,44 +1,120 @@
 <?php
-/**
- * This is an example configuration of queue.php for RabbitMQ driver
- *
- * you can add as many connections as you want
- */
 
 return [
 
-	'default'     => 'rabbitmq',
+	/*
+	|--------------------------------------------------------------------------
+	| Default Queue Driver
+	|--------------------------------------------------------------------------
+	|
+	| The Laravel queue API supports a variety of back-ends via an unified
+	| API, giving you convenient access to each back-end using the same
+	| syntax for each one. Here you may set the default queue driver.
+	|
+	| Supported: "null", "sync", "database", "beanstalkd",
+	|            "sqs", "iron", "redis"
+	|
+	*/
+
+	'default'     => env('QUEUE_DRIVER', 'sync'),
+
+	/*
+	|--------------------------------------------------------------------------
+	| Queue Connections
+	|--------------------------------------------------------------------------
+	|
+	| Here you may configure the connection information for each server that
+	| is used by your application. A default configuration has been added
+	| for each back-end shipped with Laravel. You are free to add more.
+	|
+	*/
 
 	'connections' => [
 
+		'sync'       => [
+			'driver' => 'sync',
+		],
+
+		'database'   => [
+			'driver' => 'database',
+			'table'  => 'jobs',
+			'queue'  => 'default',
+			'expire' => 60,
+		],
+
+		'beanstalkd' => [
+			'driver' => 'beanstalkd',
+			'host'   => 'localhost',
+			'queue'  => 'default',
+			'ttr'    => 60,
+		],
+
+		'sqs'        => [
+			'driver' => 'sqs',
+			'key'    => 'your-public-key',
+			'secret' => 'your-secret-key',
+			'queue'  => 'your-queue-url',
+			'region' => 'us-east-1',
+		],
+
+		'iron'       => [
+			'driver'  => 'iron',
+			'host'    => 'mq-aws-us-east-1.iron.io',
+			'token'   => 'your-token',
+			'project' => 'your-project-id',
+			'queue'   => 'your-queue-name',
+			'encrypt' => true,
+		],
+
+		'redis'      => [
+			'driver' => 'redis',
+			'queue'  => 'default',
+			'expire' => 60,
+		],
+
 		'rabbitmq' => [
-			'driver'   => 'rabbitmq',
+			'driver'          => 'rabbitmq',
 
-			'host'     => '',
-			'port'     => 5672,
+			'host'            => env('RABBITMQ_HOST', '127.0.0.1'),
+			'port'            => env('RABBITMQ_PORT', 5672),
 
-			'vhost'    => '/',
-			'login'    => '',
-			'password' => '',
+			'vhost'           => env('RABBITMQ_VHOST', '/'),
+			'login'           => env('RABBITMQ_LOGIN', 'guest'),
+			'password'        => env('RABBITMQ_PASSWORD', 'guest'),
 
-			'queue'           => '', // name of the default queue,
+			'queue'           => env('RABBITMQ_QUEUE'), // name of the default queue,
 
 			'queue_params'    => [
-				'passive'     => false,
-				'durable'     => true,
-				'exclusive'   => false,
-				'auto_delete' => false,
+				'passive'     => env('RABBITMQ_QUEUE_PASSIVE', false),
+				'durable'     => env('RABBITMQ_QUEUE_DURABLE', true),
+				'exclusive'   => env('RABBITMQ_QUEUE_EXCLUSIVE', false),
+				'auto_delete' => env('RABBITMQ_QUEUE_AUTODELETE', false),
 			],
 
 			'exchange_params' => [
-				'type'        => 'direct', // more info at http://www.rabbitmq.com/tutorials/amqp-concepts.html
-				'passive'     => false,
-				'durable'     => true, // the exchange will survive server restarts
-				'auto_delete' => false, // the exchange won't be deleted once the channel is closed.
+				'type'        => env('RABBITMQ_EXCHANGE_TYPE', 'direct'), // more info at http://www.rabbitmq.com/tutorials/amqp-concepts.html
+				'passive'     => env('RABBITMQ_EXCHANGE_PASSIVE', false),
+				'durable'     => env('RABBITMQ_EXCHANGE_DURABLE', true), // the exchange will survive server restarts
+				'auto_delete' => env('RABBITMQ_EXCHANGE_AUTODELETE', false),
 			],
 
 		],
 
 	],
 
+	/*
+	|--------------------------------------------------------------------------
+	| Failed Queue Jobs
+	|--------------------------------------------------------------------------
+	|
+	| These options configure the behavior of failed queue job logging so you
+	| can control which database and table are used to store the jobs that
+	| have failed. You may change them to any database / table you wish.
+	|
+	*/
+
+	'failed'      => [
+		'database' => 'mysql', 'table' => 'failed_jobs',
+	],
+
 ];