Skip to content
This repository was archived by the owner on Oct 11, 2022. It is now read-only.

update background-jobs documentation #4496

Merged
merged 2 commits into from
Dec 19, 2018
Merged

update background-jobs documentation #4496

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b3b6491
update background-jobs documentation
Dec 19, 2018
42b9abd
Update background-jobs.md
mxstbr Dec 19, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/workers/background-jobs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

# Background jobs

We use [`bull`](https://github.com/OptimalBits/bull) for all of our background job needs (at the moment that mostly means notification processing and emails). `bull` uses redis under the hood (see docs/setup.md for instructions on how to install redis) to store information about these jobs.
We use [`bull`](https://github.com/OptimalBits/bull) for all of our background job needs (at the moment that mostly means notification processing and emails). `bull` uses redis under the hood to store information about these jobs. (follow the instructions on [redis.io/download](https://redis.io/download) to install Redis)

All of our servers and workers connect to the same redis instance, adding and taking jobs as they see fit. In development, that's your local instance. In production, that's a remote instance hosted on [compose.com](https://compose.com). Thusly, redis acts kind of like shared global state that helps our disparate processes talk to each other.

Expand Down