Skip to content

Commit 14c05a9

Browse files
authored
Update README.md
1 parent 3f98927 commit 14c05a9

1 file changed

Lines changed: 12 additions & 12 deletions

File tree

README.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -13,11 +13,11 @@ needing to run a daemon or background process to continuously poll your queue.
1313

1414
**Full Documentation:** [qpush-bundle.readthedocs.org](http://qpush-bundle.rtfd.org)
1515

16-
##Installation
16+
## Installation
1717

1818
The bundle should be installed through composer.
1919

20-
####Add the bundle to your composer.json file
20+
#### Add the bundle to your composer.json file
2121

2222
```json
2323
{
@@ -27,7 +27,7 @@ The bundle should be installed through composer.
2727
}
2828
```
2929

30-
####Update AppKernel.php of your Symfony Application
30+
#### Update AppKernel.php of your Symfony Application
3131

3232
Add the `UecodeQPushBundle` to your kernel bootstrap sequence, in the `$bundles`
3333
array.
@@ -44,13 +44,13 @@ public function registerBundles()
4444
}
4545
```
4646

47-
##Basic Configuration:
47+
## Basic Configuration:
4848

4949
Here is a basic configuration that would create a push queue called
5050
`my_queue_name` using AWS or IronMQ. You can read about the supported providers
5151
and provider options in the [full documentation](http://qpush-bundle.rtfd.org).
5252

53-
######Example
53+
###### Example
5454

5555
```yaml
5656
#app/config.yml
@@ -76,15 +76,15 @@ uecode_qpush:
7676
7777
You may exclude aws key and secret to default to IAM role on the EC2 machine.
7878
79-
##Publishing messages to your Queue
79+
## Publishing messages to your Queue
8080
8181
Publishing messages is simple - fetch the registered Provider service from the
8282
container and call the `publish` method on the respective queue.
8383

8484
This bundle stores your messages as a json object and the publish method expects
8585
an array, typically associative.
8686

87-
######Example
87+
###### Example
8888

8989
```php
9090
// src/My/Bundle/ExampleBundle/Controller/MyController.php
@@ -102,13 +102,13 @@ public function publishAction()
102102
103103
```
104104

105-
##Working with messages from your Queue
105+
## Working with messages from your Queue
106106

107107
When a message hits your application, this bundle will dispatch a `MessageEvent`
108108
which can be handled by your services. You need to tag your services to handle
109109
these events.
110110

111-
######Example
111+
###### Example
112112
```yaml
113113
services:
114114
my_example_service:
@@ -117,7 +117,7 @@ services:
117117
- { name: uecode_qpush.event_listener, event: my_queue_key.message_received, method: onMessageReceived }
118118
```
119119

120-
######Example
120+
###### Example
121121
```php
122122
// src/My/Bundle/ExampleBundle/Service/ExampleService.php
123123
@@ -137,7 +137,7 @@ and a collection of provider specific metadata.
137137

138138
These properties are accessible through simple getters from the message object.
139139

140-
######Example
140+
###### Example
141141
```php
142142
// src/My/Bundle/ExampleBundle/Service/ExampleService.php
143143
@@ -154,7 +154,7 @@ public function onMessageReceived(MessageEvent $event)
154154
}
155155
```
156156

157-
###Cleaning up the Queue
157+
### Cleaning up the Queue
158158

159159
Once all other Event Listeners have been invoked on a `MessageEvent`, the Bundle
160160
will automatically attempt to remove the Message from your Queue for you.

0 commit comments

Comments
 (0)