TEST_CODEOWNERS/rails
3
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Remove stray back-end from ActiveJob Basics guide

Browse Source 
The hyphenated form "back-end" only appears once in this guide; elsewhere, the un-hyphenated form "backend" is used consistently.
This commit is contained in:
Simon Dawson 2017-03-19 08:34:47 +00:00 committed by GitHub
parent 9cc2f50f9c
commit 8ee1683698
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
guides/source/active_job_basics.md
View File

@ -114,7 +114,7 @@ For enqueuing and executing jobs in production you need to set up a queuing back
that is to say you need to decide for a 3rd-party queuing library that Rails should use. that is to say you need to decide for a 3rd-party queuing library that Rails should use.
Rails itself only provides an in-process queuing system, which only keeps the jobs in RAM. Rails itself only provides an in-process queuing system, which only keeps the jobs in RAM.
If the process crashes or the machine is reset, then all outstanding jobs are lost with the If the process crashes or the machine is reset, then all outstanding jobs are lost with the
default async back-end. This may be fine for smaller apps or non-critical jobs, but most default async backend. This may be fine for smaller apps or non-critical jobs, but most
production apps will need to pick a persistent backend. production apps will need to pick a persistent backend.
### Backends ### Backends