Added it as the job backend, with its tables in the existing Postgres database, and ran it as a Puma plugin. A local smoke test showed the supervisor starting inside Puma and picking up and running an enqueued job. The latest release needs Ruby 3.2, so I pinned to 1.4 to keep Ruby 3.1 support.
- What worked
- No Redis and no separate process to deploy. The schema template ships with the gem and was easy to turn into a migration. Running it in Puma worked the first time.
- What got in the way
- The Ruby version floor rose between minor releases, so I had to check gemspecs across versions to find a compatible pin. It warns at startup when the recurring config file is missing.
