Switch from Sidekiq to Solid Queue #217

New Issue

raucao · 2025-04-28T14:22:15Z

raucao commented

2025-04-28 14:22:15 +00:00

Continuing from #211:

Would be especially nice to then also remove Sidekiq (and its Redis db) and use Solid Queue instead, in order to solve #149 properly (i.e. no separate db server) and with fewer dependencies. It's even possible to do that incrementally.

Dashboard UI for Solid Queue: https://github.com/rails/mission_control-jobs

Continuing from #211: > Would be especially nice to then also remove Sidekiq (and its Redis db) and use Solid Queue instead, in order to solve #149 properly (i.e. no separate db server) and with fewer dependencies. It's even possible to do that [incrementally](https://github.com/rails/solid_queue?tab=readme-ov-file#incremental-adoption). Dashboard UI for Solid Queue: https://github.com/rails/mission_control-jobs

raucao added the

dev environment

label 2025-04-28 14:22:15 +00:00

raucao added a new dependency 2025-04-28 14:22:40 +00:00

#216 Upgrade Rails to 8.0

raucao commented

2025-04-28 14:26:50 +00:00

We can also run Solid Queue directly in Puma in development then, so we don't need a separate service/container.

See the Puma config file for an ENV var to do just that.

We can also run Solid Queue directly in Puma in development then, so we don't need a separate service/container. See the Puma config file for an ENV var to do just that.

raucao added this to the 1.0.0 Release milestone 2025-05-01 11:59:07 +00:00

raucao referenced a pull request that will close this issue

2025-05-05 07:13:43 +00:00

Switch from Sidekiq to Solid Queue #219

raucao closed this issue

2025-05-05 11:24:56 +00:00

Sign in to join this conversation.