However I do business consulting and I’ve come across several of my smaller clients who have expressed the need to migrate from their initial systems to more scalable ones. I have a tech background so I can build my own documents and it makes sense. In the coming days, we will migrate all of our 22 neeto products to Solid Queue.I’ve been using Coda for several years for businesses I have worked with and continue to do so. Solid Queue offers simplicity, requires noĪdditional infrastructure and provides visibility for managing jobs since they MissionControlController we implemented basic authentication for staging and Here, we have specified that MissionControlController would be our baseĬontroller for mission control related controllers. mission_control_passwordġ0 end 11 end 12 13 def restricted_env ? 14 Rails. We added the workaround in our test helper_methods.rb and called the method inĮach of our controller tests which were failing.ġ # app/controllers/mission_control_controller.rb 2 class MissionControlController < ApplicationController 3 before_action :authenticate!, if : :restricted_env? 4 5 private 6 7 def authenticate ! 8 authenticate_or_request_with_http_basic do | username, password | 9 username = 'solidqueue' & password = Rails. Thankfully, Ben, in the same comment, also mentioned a workaroundįor it until the fix has been added to Rails. Sometimes inconsistently overrides ActiveJob's queue_adapter setting withįor the fix.

We tried debugging and searched for solutions when we stumbled uponīen Sheldon's comment on one of Good Job's issues. On debugging, we found that theĪffected tests were all related to controllers, specifically tests inheriting Some of the tests were failing inconsistently. Apart from fixing the usual failures related to the syntax changes, Once all the above changes were done, it was obvious that a lot of tests wereįailing. Note that, although the queue adapter configuration can be removed fromĪpplication_mailer.rb once the entire application migrates to Solid Queue,Įrror handling and retry override cannot be removed because of the wayĪctionMailer::MailDeliveryJob inherits from ActiveJob::Base rather than retry_on StandardError, attempts : 3 5 end Copy The exceptions and report it to Honeybadger.ġ # application_mailer.rb 2 class ApplicationMailer < ActionMailer : : Base 3 #. On_thread_error would be called with that.įor errors in the job itself, you could try to hook into Active Job's itself.īased on the above information, we modified our SqBaseJob base class to handle Of threads and you got an error when trying to check out a new connection, ForĮxample, if you had an Active Record's thread pool too small for your number On_thread_error wasn't intended for errors on the job itself, but ratherĮrrors in the thread that's executing the job, but around the job itself. On the issue and clarified the following. However, during theĭevelopment phase, we noticed that it wasn't capturing errors. Provided by Solid Queue can be used for error handling. Here is how the file looksĢ - job_id = DisableFormJob.perform_at(deadline, self.id)Ĥ + job_id = t(wait_until: deadline).perform_later(self.id)ĩ - Sidekiq::Status.cancel(self.disable_job_id)ġ0 + SolidQueue::Job.find_by(active_job_id: self.disable_job_id).destroy!ġ2 end Copy 6.

Uncomment the file and modify it as per your needs. The installation step should have created a config/solid_queue.yml file. Run the migrations using bin/rails db:migrate.Run bin/rails generate solid_queue:install which copies the config file and.

Add gem 'solid_queue' to your Rails application's Gemfile and run.Here is a step-by-step migration guide you can use to migrate your RailsĪpplication from Sidekiq to Solid Queue. Recurring jobs, we are still using Sidekiq. We have only partially migrated to Solid Queue. Please note that Solid Queue currently doesn't support cron-style or recurring WeĬurrently have around 22 products under development and all of the products areĭecided to migrate neetoForm from Sidekiq to BigBinary is building a suite of products under neeto.

Migrate to basecamp 3