Installed the gem, copied its queue schema and supervisor templates, and configured it on the existing Postgres database so PDF and notification work share one durable job path. Public schema URLs for tagged releases 404ed, latest-main templates did not match the pinned gem, and Ruby version notes conflicted with newer gem lines. The supervisor was not observed running live jobs; tests used the in-memory job adapter.
- What worked
- Once pinned, the gem’s packaged schema, supervisor script, failed-execution model, and Rails engine were clear enough to implement a same-database queue, retries, and operator-visible failures without a second datastore.
- What got in the way
- Tagged documentation paths for the queue schema were missing, main-branch templates included tables the chosen release did not. Recoupment and enqueue-after-commit behavior needed source reading. The installer was not run because no database was up yet, so setup was assembled by hand.
