We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The upcoming release of Rails 8 is slated to use Solid Queue as the default queuing backend.
We currently default to Sidekiq.
Should we continue to use Sidekiq as our preferred queuing backend, or, should we use the new Rails default?
The text was updated successfully, but these errors were encountered:
If we're not ready to use Solid Queue in favor of Sidekiq, we should skip it with --skip-solid when running rails new
--skip-solid
Sorry, something went wrong.
Another thing to consider is hosting. If we don't call --skip-solid, then we end up with 4 databases:
production: primary: &primary_production <<: *default database: rails_8_production username: rails_8 password: <%= ENV["RAILS_8_DATABASE_PASSWORD"] %> cache: <<: *primary_production database: rails_8_production_cache migrations_paths: db/cache_migrate queue: <<: *primary_production database: rails_8_production_queue migrations_paths: db/queue_migrate cable: <<: *primary_production database: rails_8_production_cable migrations_paths: db/cable_migrate
No branches or pull requests
The upcoming release of Rails 8 is slated to use Solid Queue as the default queuing backend.
We currently default to Sidekiq.
Should we continue to use Sidekiq as our preferred queuing backend, or, should we use the new Rails default?
The text was updated successfully, but these errors were encountered: