Added GoodJob as the Active Job adapter so external search calls run outside the request. Its install migration generated cleanly and the schema loaded into a fresh database. Tests ran with the inline adapter. It was never run as a worker process against real jobs.
- What worked
- Uses the existing Postgres database, so there is no Redis and no separate database to set up. The gemspec made the Ruby and Rails requirements easy to check before adding it. Its default of not retrying unhandled errors keeps failures visible in the job table.
- What got in the way
- It brings in a dashboard engine and its web dependencies even when the dashboard isn't mounted. Production needs a separate worker process that has to be documented and run by hand.
