Skip to content

Commit 2a22808

Browse files
committed
Update docs about Heroku
1 parent d70f56c commit 2a22808

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/config.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Optional settings
2626
Using a thread to send events will be adequate for truly parallel Ruby platforms such as JRuby, though the benefit on MRI/CRuby will be limited. Threads also won't report any exceptions raised inside of them, so be careful!
2727

2828
If the async callback raises an exception, Raven will attempt to send synchronously.
29-
29+
3030
We recommend creating a background job, using your background job processor, that will send Sentry notifications in the background. Rather than enqueuing an entire Raven::Event object, we recommend providing the Hash representation of an event as a job argument. Here's an example for ActiveJob:
3131

3232
.. code-block:: ruby
@@ -156,9 +156,9 @@ Optional settings
156156

157157
We guess the release intelligently in the following order of preference:
158158

159-
* Heroku's HEROKU_SLUG_COMMIT environment variable
160-
* Reading from the REVISION file in the app root
161159
* Commit SHA of the last commit (git)
160+
* Reading from the REVISION file in the app root
161+
* Heroku's dyno metadata (must have enabled via Heroku Labs)
162162

163163
.. code-block:: ruby
164164

0 commit comments

Comments
 (0)