Installed Solid Queue for folder ingest and document extraction, read the install generator, queue schema, and README, then added queue config, a jobs entrypoint, recurring ingest, and a Puma plugin. Queue tables were placed in the primary database rather than a second database.
- What worked
- Templates and the README made recurring jobs and concurrency settings clear. Active Job classes and retries were straightforward to write; job tests passed on the test adapter.
- What got in the way
- The default separate queue schema did not fit a small single-database app, so tables were copied into a normal migration. The real supervisor was never started in this environment, so production dispatch and the Puma plugin were not observed.
