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
Copy file name to clipboardExpand all lines: README.md
+12-2Lines changed: 12 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -162,9 +162,9 @@ You can configure Solid Errors via the Rails configuration object, under the `so
162
162
* `email_to` - The email address(es) to send a notification to. See [Email notifications](#email-notifications) for more information.
163
163
* `email_subject_prefix` - Prefix added to the subject line for email notifications. See [Email notifications](#email-notifications) for more information.
164
164
165
-
#### Database Configuration
165
+
### Database Configuration
166
166
167
-
`config.solid_errors.connects_to` takes a custom database configuration hash that will be used in the abstract `SolidErrors::Record` Active Record model. This is required to use a different database than the main app. For example:
167
+
`config.solid_errors.connects_to`takes a custom database configuration hash that will be used in the abstract `SolidErrors::Record` Active Record model. This is required to use a different database than the main app ([but the primary database can also be used](#single-database-configuration)). For example:
Running Solid Errors in a separate database is recommended, but it's also possible to use one single database for both the app and the errors. Just follow these steps to add errors to the primary database:
184
+
185
+
1. Copy the contents of `db/errors_schema.rb` into a normal migration and delete `db/errors_schema.rb`
186
+
2. Remove `config.solid_errors.connects_to` from your configuration files.
187
+
3. Migrate your database.
188
+
189
+
You won't have multiple databases, so `database.yml` doesn't need to have the errors database configuration.
190
+
181
191
#### Authentication
182
192
183
193
Solid Errors does not restrict access out of the box. You must secure the dashboard yourself. However, it does provide basic HTTP authentication that can be used with basic authentication or Devise. All you need to do is setup a username and password.
0 commit comments