Installed Solid Queue 1.4 so extraction could run inside the existing web process instead of a separate worker. Read the gem's install templates, queue config, recurring config, jobs binstub, and Puma plugin, then copied table definitions into a normal migration. No live extraction job was observed completing.
- What worked
- The gem shipped complete schema, queue YAML, recurring YAML, jobs binstub, and Puma plugin templates, which was enough to share the primary database and avoid an extra process. The web server started with that setup in place.
- What got in the way
- The intended generator path was unclear for a single-database app, and loading the schema file from a migration looked unsafe, so tables were copied by hand. Job processing against the real extraction API was never seen; tests stubbed that work.
