rails_error_dashboard 0.14.2 → 0.14.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 93c0e9e0f21298eb85db1d661793709d60158c5f2c6f85b164da36b4593525ee
-  data.tar.gz: 37bae1ddaca2d502e434e0b4e6e95f6c755619598dec20f08495ce13fd0c286a
+  metadata.gz: bd115b4f0fa37f0b90cc22ceea5d5f8db5bdb59ceb40972c3d9ff70c6055a643
+  data.tar.gz: b1339930832c6e108d0e55aae93ad2cf14ed1935fa5af23bee24b9f9f4d8943d
 SHA512:
-  metadata.gz: 9c6be20b1be293c069516ed0f5f6fc19e46203224bb9aaad6be1c645f45ebb3455e03e6b3fef8d8738e4cc658dc928cd56c9f2d403d270ec6caaaa74411074b7
-  data.tar.gz: 7c1c344be4398b47faf98de6a9be675f41a86878b49404d76b73d1a5be91f046ded677c70ebb9c1f4118e8736873ea491edcfed07b6520465049b9ecb3e1066b
+  metadata.gz: 9901f9f6fcc64cf53f71cdf43545e2314fe410638eafb414619159d9955763e8251007b13aa5d02e3967ebfbe4b87fb6dff3700694d27031d67ed39c8281e8ac
+  data.tar.gz: d039b6f3796fad5884ae83bbe374671d5d2f90137747c0f404fd917cbcf8088f3b4101caf5c9b77524562b4e4c2c2ca3581d99abadfc16797d9bd35122c83afc

data/README.md

@@ -19,7 +19,7 @@ rails generate rails_error_dashboard:install
 rails db:migrate
 ```
 
-Open `/red` and raise a test exception. No monitoring account or ingestion service is required.
+Open `/red`, then send a test error from its Settings page. No monitoring account or ingestion service is required.
 
 [Try the live demo](https://rails-error-dashboard.anjan.dev) (`gandalf` / `youshallnotpass`) · [Read the documentation](https://anjanj.github.io/rails_error_dashboard/) · [View on RubyGems](https://rubygems.org/gems/rails_error_dashboard)
 
@@ -91,7 +91,7 @@ That makes RED a self-hosted Sentry alternative for teams that want Rails-specif
 
 - Store data in the application's existing PostgreSQL, MySQL/Trilogy or SQLite database.
 - Isolate monitoring writes in a separate error database.
-- Use synchronous writes, or async logging through Sidekiq or Solid Queue (GoodJob is detected for job-health stats but is not an async adapter).
+- Use synchronous writes, or async logging through your app's own Active Job backend (Sidekiq, Solid Queue, GoodJob or Rails' in-process `:async`).
 - Track several Rails applications through a shared database.
 
 No RED licence or event-ingestion fee, and no plan limits — your database is the only cap, and storm protection deliberately sheds context during floods.
@@ -619,6 +619,11 @@ Span names follow the `rails_error_dashboard.<operation>` convention, e.g. `rail
 gem 'rails_error_dashboard'
 ```
 
+RED requires Rails 7.0 or newer, Ruby 3.2 or newer, `pagy ~> 43` and `groupdate ~> 6`. An app that pins an older Pagy or groupdate must upgrade it first, or `bundle install` fails.
+
+- **Rails before 8.1.4 or 7.2.4** (every 8.0, 7.1 and 7.0 release): also add `gem "json", "< 3"`. json 3 breaks those Rails versions, and the dashboard returns 500. See [the json pin](docs/UPGRADING.md#rails-before-814-or-724-pin-json-below-3).
+- **MySQL**: load the time-zone tables (`mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root mysql`), or the charts fail.
+
 ### 2. Install with Interactive Setup
 
 ```bash
@@ -627,7 +632,9 @@ rails generate rails_error_dashboard:install
 rails db:migrate
 ```
 
-The installer guides you through optional feature selection — notifications, performance optimizations, advanced analytics. All features are opt-in.
+The installer asks about notifications and advanced analytics, then where to store errors: in your app's database (the default), a separate one, or one shared by several apps. Without a terminal (CI, Docker) it asks nothing: async logging is on, and every other optional feature is off.
+
+**Chose a separate or shared database?** Add the `config/database.yml` entry the installer prints, then run `bin/rails db:create` before `db:migrate`. See [Database Options](docs/guides/DATABASE_OPTIONS.md).
 
 ### 3. Visit your dashboard
 
@@ -635,37 +642,46 @@ The installer guides you through optional feature selection — notifications, p
 http://localhost:3000/red
 ```
 
-Default credentials: `gandalf` / `youshallnotpass`
+Default credentials: `gandalf` / `youshallnotpass`, for development and test only.
 
-**Change these before production!** Edit `config/initializers/rails_error_dashboard.rb`
+**Before you deploy anywhere else**, set `ERROR_DASHBOARD_USER` and `ERROR_DASHBOARD_PASSWORD` in that environment. Outside development and test, the app refuses to boot on the defaults. See [Dashboard Credentials](docs/guides/CONFIGURATION.md#dashboard-credentials). For the rest of what production needs (a worker, scheduled jobs, migrations on deploy), see [Running in Production](docs/PRODUCTION.md).
 
 ### 4. Test it out
 
+Open `/red/settings` and click **Send Test Error**, or raise an exception in any controller action. Errors raised at the Rails console prompt are not captured. To report one from the console, use:
+
 ```ruby
-# In Rails console or any controller
-raise "Test error from Rails Error Dashboard!"
+Rails.error.report(RuntimeError.new("Test error from Rails Error Dashboard"), handled: false)
 ```
 
+With async logging on (the default), leave the console open for a second or two so the background job can write it.
+
 [Full installation guide →](docs/QUICKSTART.md)
 
+### Upgrading
+
+```bash
+bundle update rails_error_dashboard
+bin/rails generate rails_error_dashboard:install --no-interactive
+bin/rails db:migrate
+```
+
+The installer keeps your initializer and copies only the new migrations. Some releases need a step of their own, and two of them can stop an app booting: [read the upgrade guide](docs/UPGRADING.md) before you deploy.
+
 ---
 
 ## Configuration
 
 ```ruby
 RailsErrorDashboard.configure do |config|
-  # Authentication
-  config.dashboard_username = ENV.fetch('ERROR_DASHBOARD_USER', 'gandalf')
-  config.dashboard_password = ENV.fetch('ERROR_DASHBOARD_PASSWORD', 'youshallnotpass')
-
-  # Or use your existing auth (Devise, Warden, etc.):
+  # Dashboard login: set ERROR_DASHBOARD_USER and ERROR_DASHBOARD_PASSWORD outside
+  # development and test (the gem reads them itself). Or use your existing auth:
   # config.authenticate_with = -> { warden.authenticated? }
 
   # Optional features — enable as needed
   config.enable_slack_notifications = true
   config.slack_webhook_url = ENV['SLACK_WEBHOOK_URL']
-  config.async_logging = true
-  config.async_adapter = :sidekiq  # or :solid_queue, :async
+  config.async_logging = true  # jobs run on your app's Active Job adapter; production needs a worker
 end
 ```
 
@@ -673,7 +689,7 @@ end
 
 **Multi-App Support** — Track errors from multiple Rails apps in a single shared database. Auto-detects app name, supports per-app filtering. [Multi-App guide →](docs/MULTI_APP_PERFORMANCE.md)
 
-**OpenTelemetry Export** — Emit error-capture operations as OTel spans to Datadog, Honeycomb, or Jaeger. Add `gem "opentelemetry-api"` and set `config.enable_otel_export = true`. See [OpenTelemetry Export](#opentelemetry-export--emit-gem-operations-as-spans) above for full options.
+**OpenTelemetry Export** — Emit error-capture operations as OTel spans to Datadog, Honeycomb, or Jaeger. Add `gem "opentelemetry-api"` and set `config.enable_otel_export = true`. See **OpenTelemetry Export** under [Features](#features) above for the full options.
 
 ---
 
@@ -714,7 +730,7 @@ RED translates through its own private I18n backend, so it never reads, writes o
 ## FAQ
 
 **Does Rails Error Dashboard support a separate database for errors?**
-Yes. You can store errors in your app's existing database (shared) **or** in a dedicated, isolated database (separate). Set `config.use_separate_database = true` (or `USE_SEPARATE_ERROR_DB=true`) and point it at a separate connection — the engine routes all of its tables through `connects_to`, keeping error data fully isolated from your app data. Both modes are first-class and covered by the [Database Options guide](docs/guides/DATABASE_OPTIONS.md).
+Yes. You can store errors in your app's existing database **or** in a dedicated one. Choose it at the installer's database prompt (or pass `--separate-database`), then add the `error_dashboard` entry it prints to `config/database.yml` for every environment. The engine routes all of its tables through `connects_to`, keeping error data isolated from your app data. Both modes are first-class and covered by the [Database Options guide](docs/guides/DATABASE_OPTIONS.md).
 
 **Which databases does it work with?**
 SQLite, PostgreSQL, and MySQL/Trilogy — in either shared or separate-database mode.
@@ -729,13 +745,13 @@ Yes — local **and** instance variables at the moment the exception is raised,
 No. Storm protection (a circuit breaker with adaptive sampling, **ON by default**) makes the gem degrade itself first during error floods — occurrence counts stay exact while it sheds the expensive work, and a Storm History page shows exactly what was shed. There is no I/O on the hot path — the check is a digest and an atomic increment.
 
 **Does it work with my background jobs?**
-Yes — errors raised in jobs are captured, and it can log errors asynchronously through Sidekiq or SolidQueue (or the in-process `:async` adapter). Sidekiq, SolidQueue and GoodJob are all auto-detected for the job-queue stats stored on each error.
+Yes — errors raised in jobs are captured, and it can log errors asynchronously through your app's Active Job adapter (Sidekiq, Solid Queue, GoodJob or the in-process `:async`). In production, run a worker for the `default` and `error_notifications` queues. Sidekiq, Solid Queue and GoodJob are all auto-detected for the job-queue stats stored on each error.
 
 **Does it work with my authentication?**
 Yes — HTTP Basic Auth out of the box, or a custom `authenticate_with` lambda that integrates with Devise, Warden, or session-based auth.
 
 **Can it track more than one app?**
-Yes — multi-app support tracks errors from multiple Rails apps in one dashboard with per-app filtering.
+Yes — apps that point at the same error database share one dashboard, with per-app filtering.
 
 **What Rails and Ruby versions are supported?**
 Rails 7.0–8.1 and Ruby 3.2–4.0.
@@ -747,6 +763,8 @@ Rails 7.0–8.1 and Ruby 3.2–4.0.
 ### Getting Started
 - **[Quickstart Guide](docs/QUICKSTART.md)** — 5-minute setup
 - **[Configuration](docs/guides/CONFIGURATION.md)** — All configuration options
+- **[Upgrading](docs/UPGRADING.md)** — The upgrade, and the releases that need a step
+- **[Running in Production](docs/PRODUCTION.md)** — A worker, scheduled jobs and the other things RED needs before the first deploy
 - **[Uninstalling](docs/UNINSTALL.md)** — Clean removal
 
 ### Features

data/app/helpers/rails_error_dashboard/application_helper.rb

@@ -1,5 +1,13 @@
 module RailsErrorDashboard
   module ApplicationHelper
+    # Problems in config/queue.yml that stop RED's jobs in this environment:
+    # empty when the config is fine, or when Solid Queue doesn't run RED's jobs.
+    def red_solid_queue_problems
+      Services::SolidQueueConfigCheck.current_problems
+    rescue StandardError
+      []
+    end
+
     # Returns the host app's CSP nonce (if any) so inline <script> tags pass strict CSP.
     # Falls back to nil when the host has no CSP configured — in that case the script tag
     # works without a nonce attribute. Strict CSPs (script-src 'self' 'nonce-...') require

data/app/jobs/rails_error_dashboard/retention_cleanup_job.rb

@@ -33,6 +33,32 @@ module RailsErrorDashboard
       )
     end
 
+    # Deletes error logs and everything that references them: dependents first,
+    # all in batches. Occurrences, comments and cascade patterns hold foreign
+    # keys to the log, so deleting the logs first fails, and one unbounded
+    # DELETE would lock the table. Public because error_dashboard:cleanup_resolved
+    # deletes the same way.
+    #
+    # @param scope [ActiveRecord::Relation] the ErrorLog rows to delete
+    # @return [Integer] number of error logs deleted
+    def self.delete_with_dependents(scope)
+      ids = scope.select(:id)
+
+      ErrorOccurrence.where(error_log_id: ids).in_batches(of: 1000).delete_all
+      # Hour buckets for storm-shed events. Listed explicitly because delete_all
+      # does not fire the has_many :dependent callback on ErrorLog -- without
+      # this line the buckets outlive the group they describe, forever.
+      EventCount.where(error_log_id: ids).in_batches(of: 1000).delete_all if EventCount.table_exists?
+      ErrorComment.where(error_log_id: ids).in_batches(of: 1000).delete_all
+      CascadePattern.where(parent_error_id: ids)
+                    .or(CascadePattern.where(child_error_id: ids))
+                    .in_batches(of: 1000).delete_all
+
+      deleted = 0
+      scope.in_batches(of: 1000) { |batch| deleted += batch.delete_all }
+      deleted
+    end
+
     # @return [Integer] number of errors deleted
     def perform
       retention_days = RailsErrorDashboard.configuration.retention_days
@@ -52,29 +78,7 @@ module RailsErrorDashboard
       expired_scope = self.class.expired_scope(cutoff)
       return 0 if expired_scope.none?
 
-      deleted_count = 0
-
-      # Delete dependents first, then errors — all in batches to prevent table locks
-      expired_ids_scope = expired_scope.select(:id)
-
-      # Batch delete dependent records (occurrences, comments, cascade patterns)
-      ErrorOccurrence.where(error_log_id: expired_ids_scope).in_batches(of: 1000).delete_all
-      # Hour buckets for storm-shed events. Listed explicitly because this job
-      # deletes with delete_all, which does not fire the has_many :dependent
-      # callback on ErrorLog -- without this line the buckets outlive the group
-      # they describe, forever. The migration's own comment promised this
-      # pruning before the code existed.
-      EventCount.where(error_log_id: expired_ids_scope).in_batches(of: 1000).delete_all if EventCount.table_exists?
-      ErrorComment.where(error_log_id: expired_ids_scope).in_batches(of: 1000).delete_all
-      CascadePattern.where(parent_error_id: expired_ids_scope)
-                    .or(CascadePattern.where(child_error_id: expired_ids_scope))
-                    .in_batches(of: 1000).delete_all
-
-      # Now batch delete the error logs themselves
-      expired_scope.in_batches(of: 1000) do |batch|
-        batch_size = batch.delete_all
-        deleted_count += batch_size
-      end
+      deleted_count = self.class.delete_with_dependents(expired_scope)
 
       # delete_all skips callbacks, and the stat cards are cached.
       Services::AnalyticsCacheManager.clear if deleted_count > 0

data/app/views/layouts/rails_error_dashboard.html.erb

@@ -1335,6 +1335,19 @@ tr[data-red-row-href]:hover .sev-bar { opacity: 1 !important; }
             </div>
             <script<%= " nonce=\"#{red_csp_nonce}\"".html_safe if red_csp_nonce %>>try { if (sessionStorage.getItem('red_dismiss_creds_warning') === '1') { document.getElementById('security-warning').style.display = 'none'; } } catch(e) {}</script>
           <% end %>
+          <% solid_queue_problems = red_solid_queue_problems %>
+          <% if solid_queue_problems.any? %>
+            <div id="solid-queue-warning" class="alert alert-warning" style="display: flex; align-items: flex-start; gap: 10px; margin-top: var(--space-2); margin-bottom: var(--space-4); border-left: 4px solid var(--status-warning);">
+              <i class="bi bi-exclamation-triangle-fill" style="font-size: 18px; flex-shrink: 0;"></i>
+              <div style="flex: 1;">
+                <strong><%= red_t("red.banners.solid_queue.label") %></strong> <%= red_t("red.banners.solid_queue.body_html") %>
+                <ul style="margin: var(--space-2) 0; padding-left: var(--space-5); font-family: var(--font-mono); font-size: 12px;">
+                  <% solid_queue_problems.each do |problem| %><li><%= problem %></li><% end %>
+                </ul>
+                <a href="<%= RailsErrorDashboard::Services::SolidQueueConfigCheck::GUIDE_URL %>" target="_blank" rel="noopener"><%= red_t("red.banners.solid_queue.guide") %></a>
+              </div>
+            </div>
+          <% end %>
           <% if defined?(@storm_banner_event) && @storm_banner_event %>
             <% storm_active = @storm_banner_event.active? %>
             <div id="storm-banner" class="alert <%= storm_active ? 'alert-danger' : 'alert-info' %>" style="display: flex; align-items: center; gap: 10px; margin-top: var(--space-2); margin-bottom: var(--space-4); border-left: 4px solid <%= storm_active ? 'var(--status-critical)' : 'var(--status-info)' %>;">

data/config/locales/de.yml

@@ -87,6 +87,10 @@ de:
           <code>ERROR_DASHBOARD_PASSWORD</code> oder konfigurieren Sie <code>authenticate_with</code>
           in Ihrem Initializer.
         dismiss: Für diese Sitzung ausblenden
+      solid_queue:
+        label: "Solid Queue führt die Jobs von RED nicht aus."
+        body_html: "Im Hintergrund erfasste Fehler und Benachrichtigungen warten in der Warteschlange, bis <code>config/queue.yml</code> korrigiert ist. Führen Sie <code>bin/rails error_dashboard:verify</code> aus, um die Korrektur zu sehen, und starten Sie die App danach neu."
+        guide: "Was RED von Solid Queue braucht"
       storm:
         active_title: Fehlersturm im Gange
         recent_title: Sturmschutz war kürzlich aktiv

data/config/locales/en.yml

@@ -155,6 +155,11 @@ en:
           initializer.
         dismiss: "Dismiss for this session"
 
+      solid_queue:
+        # Shown when Solid Queue runs RED's jobs with a config/queue.yml that never would.
+        label: "Solid Queue won't run RED's jobs."
+        body_html: "Errors captured in the background and notifications wait in the queue until <code>config/queue.yml</code> is fixed. Run <code>bin/rails error_dashboard:verify</code> for the fix, then restart."
+        guide: "What RED needs from Solid Queue"
       storm:
         # Whole sentences, not fragments. The English original assembled these
         # from a stem plus a conditional clause, which cannot be reordered into

data/config/locales/es.yml

@@ -86,6 +86,10 @@ es:
           Defina las variables de entorno <code>ERROR_DASHBOARD_USER</code> y <code>ERROR_DASHBOARD_PASSWORD</code>,
           o configure <code>authenticate_with</code> en su initializer.
         dismiss: Ocultar durante esta sesión
+      solid_queue:
+        label: "Solid Queue no ejecutará los trabajos de RED."
+        body_html: "Los errores capturados en segundo plano y las notificaciones esperan en la cola hasta que se corrija <code>config/queue.yml</code>. Ejecute <code>bin/rails error_dashboard:verify</code> para ver la corrección y luego reinicie."
+        guide: "Lo que RED necesita de Solid Queue"
       storm:
         active_title: Tormenta de errores en curso
         recent_title: La protección ante tormentas se activó recientemente

data/config/locales/fr.yml

@@ -87,6 +87,10 @@ fr:
           et <code>ERROR_DASHBOARD_PASSWORD</code>, ou configurez <code>authenticate_with</code>
           dans votre initializer.
         dismiss: Masquer pour cette session
+      solid_queue:
+        label: "Solid Queue n'exécutera pas les tâches de RED."
+        body_html: "Les erreurs capturées en arrière-plan et les notifications restent en file d'attente tant que <code>config/queue.yml</code> n'est pas corrigé. Lancez <code>bin/rails error_dashboard:verify</code> pour voir la correction, puis redémarrez."
+        guide: "Ce dont RED a besoin de Solid Queue"
       storm:
         active_title: Tempête d'erreurs en cours
         recent_title: La protection anti-tempête s'est déclenchée récemment

data/config/locales/it.yml

@@ -86,6 +86,10 @@ it:
           Imposta le variabili d'ambiente <code>ERROR_DASHBOARD_USER</code> e <code>ERROR_DASHBOARD_PASSWORD</code>
           oppure configura <code>authenticate_with</code> nel tuo inizializzatore.
         dismiss: Nascondi per questa sessione
+      solid_queue:
+        label: "Solid Queue non eseguirà i job di RED."
+        body_html: "Gli errori acquisiti in background e le notifiche restano in coda finché <code>config/queue.yml</code> non viene corretto. Esegui <code>bin/rails error_dashboard:verify</code> per vedere la correzione, poi riavvia."
+        guide: "Cosa serve a RED da Solid Queue"
       storm:
         active_title: Tempesta di errori in corso
         recent_title: Protezione dalle tempeste attivata di recente

data/config/locales/ja.yml

@@ -86,6 +86,10 @@ ja:
           と <code>ERROR_DASHBOARD_PASSWORD</code> を設定するか、イニシャライザで <code>authenticate_with</code>
           を設定してください。
         dismiss: このセッションでは表示しない
+      solid_queue:
+        label: "Solid Queue は RED のジョブを実行しません。"
+        body_html: "<code>config/queue.yml</code> を修正するまで、バックグラウンドで記録されたエラーと通知はキューで待機します。<code>bin/rails error_dashboard:verify</code> を実行して修正方法を確認し、再起動してください。"
+        guide: "RED が Solid Queue に必要とするもの"
       storm:
         active_title: エラーストームが発生中です
         recent_title: ストーム保護が最近作動しました

data/config/locales/pl.yml

@@ -86,6 +86,10 @@ pl:
           Ustaw zmienne środowiskowe <code>ERROR_DASHBOARD_USER</code> i <code>ERROR_DASHBOARD_PASSWORD</code>
           albo skonfiguruj <code>authenticate_with</code> w swoim inicjalizatorze.
         dismiss: Ukryj na czas tej sesji
+      solid_queue:
+        label: "Solid Queue nie uruchomi zadań RED."
+        body_html: "Błędy przechwycone w tle i powiadomienia czekają w kolejce, dopóki <code>config/queue.yml</code> nie zostanie poprawiony. Uruchom <code>bin/rails error_dashboard:verify</code>, aby zobaczyć poprawkę, a następnie zrestartuj aplikację."
+        guide: "Czego RED potrzebuje od Solid Queue"
       storm:
         active_title: Trwa sztorm błędów
         recent_title: Ochrona przed sztormem zadziałała niedawno

data/config/locales/pt-BR.yml

@@ -86,6 +86,10 @@ pt-BR:
           Defina as variáveis de ambiente <code>ERROR_DASHBOARD_USER</code> e <code>ERROR_DASHBOARD_PASSWORD</code>,
           ou configure <code>authenticate_with</code> no seu initializer.
         dismiss: Ocultar nesta sessão
+      solid_queue:
+        label: "O Solid Queue não executará os jobs do RED."
+        body_html: "Erros capturados em segundo plano e notificações aguardam na fila até que <code>config/queue.yml</code> seja corrigido. Execute <code>bin/rails error_dashboard:verify</code> para ver a correção e reinicie."
+        guide: "O que o RED precisa do Solid Queue"
       storm:
         active_title: Tempestade de erros em andamento
         recent_title: A proteção contra tempestades foi acionada recentemente

data/config/locales/ru.yml

@@ -86,6 +86,10 @@ ru:
           Задайте переменные окружения <code>ERROR_DASHBOARD_USER</code> и <code>ERROR_DASHBOARD_PASSWORD</code>
           или настройте <code>authenticate_with</code> в инициализаторе.
         dismiss: Скрыть до конца сессии
+      solid_queue:
+        label: "Solid Queue не будет выполнять задания RED."
+        body_html: "Ошибки, записанные в фоне, и уведомления ждут в очереди, пока не исправлен <code>config/queue.yml</code>. Запустите <code>bin/rails error_dashboard:verify</code>, чтобы увидеть исправление, затем перезапустите приложение."
+        guide: "Что RED нужно от Solid Queue"
       storm:
         active_title: Идёт шторм ошибок
         recent_title: Недавно сработала защита от шторма

data/config/locales/uk.yml

@@ -86,6 +86,10 @@ uk:
           Встановіть змінні середовища <code>ERROR_DASHBOARD_USER</code> і <code>ERROR_DASHBOARD_PASSWORD</code>
           або налаштуйте <code>authenticate_with</code> у своєму ініціалізаторі.
         dismiss: Приховати для цієї сесії
+      solid_queue:
+        label: "Solid Queue не виконуватиме завдання RED."
+        body_html: "Помилки, записані у фоні, і сповіщення чекають у черзі, доки не виправлено <code>config/queue.yml</code>. Запустіть <code>bin/rails error_dashboard:verify</code>, щоб побачити виправлення, потім перезапустіть застосунок."
+        guide: "Що RED потрібно від Solid Queue"
       storm:
         active_title: Триває шторм помилок
         recent_title: Нещодавно спрацював захист від штормів

data/config/locales/zh-CN.yml

@@ -85,6 +85,10 @@ zh-CN:
         body_html: 你正在使用默认凭据（gandalf/youshallnotpass）。请设置环境变量 <code>ERROR_DASHBOARD_USER</code>
           和 <code>ERROR_DASHBOARD_PASSWORD</code>，或在初始化文件中配置 <code>authenticate_with</code>。
         dismiss: 本次会话内不再提示
+      solid_queue:
+        label: "Solid Queue 不会运行 RED 的任务。"
+        body_html: "在修复 <code>config/queue.yml</code> 之前，后台捕获的错误和通知会一直在队列中等待。运行 <code>bin/rails error_dashboard:verify</code> 查看修复方法，然后重启应用。"
+        guide: "RED 对 Solid Queue 的要求"
       storm:
         active_title: 错误风暴进行中
         recent_title: 近期触发过风暴保护

data/db/migrate/20251225074653_remove_environment_from_error_logs.rb

@@ -3,6 +3,15 @@ class RemoveEnvironmentFromErrorLogs < ActiveRecord::Migration[7.0]
     # Skip if squashed migration ran (column never existed) or already removed
     return unless column_exists?(:rails_error_dashboard_error_logs, :environment)
 
+    # Only the v0.1.x column is removed: it was NOT NULL. The column
+    # AddEnvironmentToErrorLogs adds back (0.11.0) is nullable and holds real
+    # data. This migration replays over it whenever RED's migrations run
+    # against tables that already exist (an app joining a shared error
+    # database runs its own renumbered copy of every migration), and dropping
+    # it there wiped every error's environment.
+    environment = columns(:rails_error_dashboard_error_logs).find { |column| column.name == "environment" }
+    return if environment.nil? || environment.null
+
     # Remove composite index first
     remove_index :rails_error_dashboard_error_logs,
                  name: 'index_error_logs_on_environment_and_occurred_at',

data/lib/generators/rails_error_dashboard/install/install_generator.rb

@@ -15,7 +15,7 @@ module RailsErrorDashboard
       class_option :pagerduty, type: :boolean, default: false, desc: "Enable PagerDuty notifications"
       class_option :webhooks, type: :boolean, default: false, desc: "Enable webhook notifications"
       # Performance options
-      class_option :async_logging, type: :boolean, default: true, desc: "Enable async error logging (default: true, uses Rails :async adapter — no extra infrastructure needed)"
+      class_option :async_logging, type: :boolean, default: true, desc: "Enable async error logging (default: true; jobs run on your app's Active Job adapter, so production needs a worker)"
       class_option :error_sampling, type: :boolean, default: false, desc: "Enable error sampling (reduce volume)"
       class_option :separate_database, type: :boolean, default: false, desc: "Use separate database for errors"
       class_option :database, type: :string, default: nil, desc: "Database name to use for errors (e.g., 'error_dashboard')"
@@ -58,7 +58,7 @@ module RailsErrorDashboard
 
         if quick_mode?
           @selected_features = build_quick_defaults
-          say "  Using sensible defaults (analytics ON, notifications OFF, breadcrumbs OFF)", :green
+          say "  Using sensible defaults (analytics, breadcrumbs ON, system health ON, 50% sampling; notifications OFF)", :green
           return
         end
 
@@ -131,7 +131,10 @@ module RailsErrorDashboard
         advanced_keys = %i[async_logging error_sampling breadcrumbs system_health
                            source_code_integration git_blame swallowed_exceptions
                            crash_capture diagnostic_dump]
-        any_advanced_cli_flag = advanced_keys.any? { |k| options[k] }
+        # A flag the user passed, not an option left at its default: async_logging
+        # defaults to true, so "is any of these set?" was always yes and this
+        # question was never asked.
+        any_advanced_cli_flag = advanced_keys.any? { |k| options[k] != self.class.class_options[k]&.default }
 
         say "\n[3/3] Advanced Options (performance tuning & diagnostics)", :cyan
         say "    Async logging, error sampling, breadcrumbs, system health,", :white
@@ -169,8 +172,10 @@ module RailsErrorDashboard
             advanced_features.each do |f|
               say "\n    #{f[:name]}", :cyan
               say "    #{f[:desc]}", :white
-              r = ask("    Enable? (y/N):", :yellow, limited_to: [ "y", "Y", "n", "N", "" ])
-              @selected_features[f[:key]] = r.downcase == "y"
+              # Async logging is on unless declined, as it is without this question.
+              default_on = f[:key] == :async_logging
+              r = ask("    Enable? (#{default_on ? 'Y/n' : 'y/N'}):", :yellow, limited_to: [ "y", "Y", "n", "N", "" ])
+              @selected_features[f[:key]] = default_on ? r.downcase != "n" : r.downcase == "y"
               if @selected_features[f[:key]] && f[:key] == :swallowed_exceptions && RUBY_VERSION < "3.3"
                 say "    ⚠ Requires Ruby 3.3+ (you have #{RUBY_VERSION}) — will activate after upgrade", :yellow
               end
@@ -293,7 +298,9 @@ module RailsErrorDashboard
         @enable_webhooks = @selected_features&.dig(:webhooks) || options[:webhooks]
 
         # Performance
-        @enable_async_logging = @selected_features&.dig(:async_logging) || options[:async_logging]
+        # An answer, when there was one, wins: `answer || default` turned a "no"
+        # into the default's "yes".
+        @enable_async_logging = @selected_features&.key?(:async_logging) ? @selected_features[:async_logging] : options[:async_logging]
         @enable_error_sampling = @selected_features&.dig(:error_sampling) || options[:error_sampling]
 
         # Database mode (set by select_database_mode or CLI flags)
@@ -383,7 +390,7 @@ module RailsErrorDashboard
           return
         end
 
-        route "mount RailsErrorDashboard::Engine => '/red'  # RED (Rails Error Dashboard) — also works at /error_dashboard"
+        route "mount RailsErrorDashboard::Engine => '/red'  # RED (Rails Error Dashboard)"
       end
 
       def show_feature_summary
@@ -400,7 +407,7 @@ module RailsErrorDashboard
         say "  ✓ Dashboard UI", :green
         say "  ✓ Real-time Updates", :green
         say "  ✓ Analytics", :green
-        say "  ✓ Async Logging (Rails :async adapter — no extra infrastructure needed)", :green
+        say "  ✓ Async Logging (runs on your app's Active Job adapter)", :green
 
         # Count optional features enabled
         enabled_count = 0
@@ -477,14 +484,11 @@ module RailsErrorDashboard
         say "  → Set PAGERDUTY_INTEGRATION_KEY in .env", :yellow if @enable_pagerduty
         say "  → Set WEBHOOK_URLS in .env", :yellow if @enable_webhooks
         if @enable_async_logging
-          # Check which async adapter is in use — only warn about external workers when needed
-          async_section = File.exist?(File.join(destination_root, "config/initializers/rails_error_dashboard.rb")) &&
-                          File.read(File.join(destination_root, "config/initializers/rails_error_dashboard.rb"))
-          if async_section && (async_section.include?("async_adapter = :sidekiq") || async_section.include?("async_adapter = :solid_queue"))
-            say "  → Ensure your background worker (Sidekiq/SolidQueue) is running for async logging", :yellow
-          else
-            say "  ✓ Async logging uses Rails :async adapter — no extra process needed", :green
-          end
+          # RED's jobs run on the app's own Active Job adapter; async_adapter only
+          # feeds validation and the Settings page. Rails 8 production uses Solid
+          # Queue, which needs a worker, so don't promise that none is needed.
+          say "  → Async logging enqueues on your app's config.active_job.queue_adapter.", :yellow
+          say "    Run a worker for the default and error_notifications queues, or set config.async_logging = false.", :yellow
         end
 
         # Database-specific instructions
@@ -496,28 +500,29 @@ module RailsErrorDashboard
         say "Next Steps:", :cyan
         if @enable_separate_database
           say "  1. Add the database.yml entry shown above"
-          say "  2. Run: rails db:create:error_dashboard"
+          say "  2. Run: rails db:create:#{@database_name}"
           if @enable_multi_app
             say "  3. Run migrations (only needed on the FIRST app):"
-            say "     rails db:migrate:error_dashboard"
+            say "     rails db:migrate:#{@database_name}"
           else
-            say "  3. Run: rails db:migrate:error_dashboard"
+            say "  3. Run: rails db:migrate:#{@database_name}"
           end
-          say "  4. Update credentials in config/initializers/rails_error_dashboard.rb"
+          say "  4. Before deploying: set ERROR_DASHBOARD_USER and ERROR_DASHBOARD_PASSWORD there"
           say "  5. Restart your Rails server"
           say "  6. Visit http://localhost:3000/red"
           say "  7. Verify: rails error_dashboard:verify"
         else
           say "  1. Run: rails db:migrate"
-          say "  2. Update credentials in config/initializers/rails_error_dashboard.rb"
+          say "  2. Before deploying: set ERROR_DASHBOARD_USER and ERROR_DASHBOARD_PASSWORD there"
           say "  3. Restart your Rails server"
           say "  4. Visit http://localhost:3000/red"
         end
         say "Authentication:", :cyan
-        say "  Default: HTTP Basic Auth (gandalf/youshallnotpass)", :white
+        say "  Default: HTTP Basic Auth, gandalf/youshallnotpass in development and test only", :white
+        say "  Elsewhere: set ERROR_DASHBOARD_USER and ERROR_DASHBOARD_PASSWORD, or the app won't boot", :white
         say "  Devise/Warden: config.authenticate_with = -> { warden.authenticated? }", :white
         say "  Session-based: config.authenticate_with = -> { session[:admin] == true }", :white
-        say "  See: https://github.com/AnjanJ/rails_error_dashboard/blob/main/docs/guides/CONFIGURATION.md#custom-authentication", :white
+        say "  See: https://github.com/AnjanJ/rails_error_dashboard/blob/main/docs/guides/CONFIGURATION.md#dashboard-credentials", :white
         say "\n"
         say "Issue Tracking (optional):", :cyan
         say "  Create a dedicated RED (Rails Error Dashboard) bot account on your platform:", :white
@@ -549,7 +554,7 @@ module RailsErrorDashboard
 
       def build_quick_defaults
         {
-          # Async ON (built-in Rails :async adapter, zero infrastructure)
+          # Async ON (runs on the app's Active Job adapter)
           async_logging: true,
           # All analytics ON — run at query/background time, zero request-path overhead
           baseline_alerts: true,
@@ -597,33 +602,23 @@ module RailsErrorDashboard
           say "  # Separate error database", :white
         end
 
-        say "\n  development:", :cyan
-        say "    primary:", :white
-        say "      <<: *default", :white
-        say "      database: #{app_name_snake}_development", :white
-        say "    error_dashboard:", :white
-        say "      <<: *default", :white
-        if @enable_multi_app
-          shared_db_base = @shared_db_name || "shared_errors"
-          say "      database: #{shared_db_base}_development", :white
-        else
-          say "      database: #{app_name_snake}_errors_development", :white
-        end
-        say "      migrations_paths: db/error_dashboard_migrate", :white
-
-        say "\n  production:", :cyan
-        say "    primary:", :white
-        say "      <<: *default", :white
-        say "      database: #{app_name_snake}_production", :white
-        say "    error_dashboard:", :white
-        say "      <<: *default", :white
-        if @enable_multi_app
-          shared_db_base = @shared_db_name || "shared_errors"
-          say "      database: #{shared_db_base}_production", :white
-        else
-          say "      database: #{app_name_snake}_errors_production", :white
+        # Every environment the app boots in needs the entry, test included:
+        # without it RED falls back to the main database and records nothing.
+        %w[development test production].each do |env|
+          say "\n  #{env}:", :cyan
+          say "    primary:", :white
+          say "      <<: *default", :white
+          say "      database: #{app_name_snake}_#{env}", :white
+          say "    #{@database_name}:", :white
+          say "      <<: *default", :white
+          if @enable_multi_app
+            shared_db_base = @shared_db_name || "shared_errors"
+            say "      database: #{shared_db_base}_#{env}", :white
+          else
+            say "      database: #{app_name_snake}_errors_#{env}", :white
+          end
+          say "      migrations_paths: db/error_dashboard_migrate", :white
         end
-        say "      migrations_paths: db/error_dashboard_migrate", :white
         say "\n"
 
         if @enable_multi_app