Skip to content

Commit fe1d4cf

Browse files
committed
update readme and add project name
1 parent ac2583a commit fe1d4cf

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

samples/bullmq-bullboard-redis/README.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,11 @@
22

33
This sample project demonstrates how to deploy a BullMQ message queue on top of managed Redis with a queue processor and a dashboard to monitor the queue.
44

5-
Once your app is up and running you can go to the `/admin/queues` route for the `bullmq-bullboard` service to see the BullBoard dashboard and use the username `admin` and the password you set in step 2 to log in.
5+
Once your app is up and running you can go to the `/board` route for the `board` service to see the Bull Board dashboard and use the username `admin` and the password you set to log in (see [Deploying](#deploying)).
66

7-
To add a job to the queue, you can go to the `/add` route of the `bullmq-api` service.
7+
To add a job to the queue, you can go to the `/add` route of the `api` service. This will use some default values so you can test things out. You can also see an example of a post request in the [sample http request](./api/add.test.http) file.
8+
9+
The `worker` service is the queue processor that will process the jobs added to the queue. You can see in the `compose.yaml` file that the `worker` service is set to scale to 2 instances. This means that there will be 2 workers processing jobs from the queue. You can set this to your desired number of workers, but we wanted to show how you can increase the number of workers to handle more jobs.
810

911

1012
## Prerequisites

samples/bullmq-bullboard-redis/compose.dev.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
version: '3.9'
2-
name: bullmq-bullboard-redis
2+
name: bullmq
33

44
services:
55
board:

0 commit comments

Comments
 (0)