You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* The `endpoint` and `session_endpoint` configuration options are now deprecated but still supported. The [`set_endpoints`](https://docs.bugsnag.com/platforms/ruby/other/configuration-options#endpoints) method should be used instead. Note that session tracking will be disabled if the notify endpoint is configured but the sessions endpoint is not - this is to avoid inadvertently sending session payloads to the wrong server.
The Bugsnag exception reporter for Ruby gives you instant notification of exceptions thrown from your **[Rails](https://www.bugsnag.com/platforms/rails)**, **Sinatra**, **Rack** or **plain Ruby** app. Any uncaught exceptions will trigger a notification to be sent to your Bugsnag project.
@@ -10,6 +10,7 @@ The Bugsnag exception reporter for Ruby gives you instant notification of except
10
10
* Report handled exceptions
11
11
* Attach user information to determine how many people are affected by a crash
12
12
* Send customized diagnostic data
13
+
* Track events that occur leading up to a crash
13
14
14
15
## Getting started
15
16
@@ -33,7 +34,7 @@ The Bugsnag exception reporter for Ruby gives you instant notification of except
* Check out some [example apps integrated with Bugsnag](https://github.com/bugsnag/bugsnag-example-apps/tree/master/apps/ruby) using Rails, Sinatra, Padrino, and more.
37
+
* Check out some [example apps integrated with Bugsnag](https://github.com/bugsnag/bugsnag-ruby/tree/master/example) using Rails, Sinatra, Padrino, and more.
37
38
*[Search open and closed issues](https://github.com/bugsnag/bugsnag-ruby/issues?utf8=✓&q=is%3Aissue) for similar problems
38
39
*[Report a bug or request a feature](https://github.com/bugsnag/bugsnag-ruby/issues/new)
Copy file name to clipboardExpand all lines: example/rails-51/README.md
+21-2Lines changed: 21 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,18 +56,37 @@ Navigate to the `/sidekiq` page and run any of the examples using the links prov
56
56
57
57
The worker code can be found in `app/workers/sidekiq_workers.rb`.
58
58
59
+
To process the jobs, run Sidekiq using the following command:
60
+
61
+
```shell
62
+
bundle exec sidekiq
63
+
```
64
+
59
65
## Que in Rails
60
66
61
67
Que requires a database backend in order to queue jobs. By default this database will be PostgreSQL although this can be changed via options as detailed in [the que documentation](https://github.com/chanks/que).
62
68
63
-
Once PostgreSQL is set up as detailed using [the PostgreSQL documentation](https://www.postgresql.org/docs/), ensure Que can connect correctly before running and of the following examples. You may need to configure your connection in the `config/database.yml` file.
69
+
Once PostgreSQL is set up as detailed using [the PostgreSQL documentation](https://www.postgresql.org/docs/), ensure Que can connect correctly before running any of the following examples which reference a `quedb` that can be created with the following command:
70
+
71
+
```shell
72
+
createdb quedb
73
+
```
74
+
75
+
You can configure your connection in the `config/database.yml` file.
64
76
65
77
### Configuration
66
78
79
+
All tasks run with Que should set the rails environment to `que`. This ensures that the correct database and connection settings are used.
80
+
Do this by prepending `RAILS_ENV=que` before each command, or run:
81
+
82
+
```shell
83
+
export RAILS_ENV=que
84
+
```
85
+
67
86
Ensure that the initial Que setup is complete by running:
0 commit comments