remove activejob configuration and base class

Except for specific and relatively uncommon circumstances, Sidekiq has a perfectly sufficient API and commonly used conventions, and doesn't need an abstraction/wrapper around it.
lockstep · Jun 19, 2018 · 59cf38d · 59cf38d
1 parent 22f37dd
commit 59cf38d
Show file tree

Hide file tree

Showing 3 changed files with 1 addition and 8 deletions.
diff --git a/app/jobs/application_job.rb b/app/jobs/application_job.rb
diff --git a/config/application.rb b/config/application.rb
@@ -19,9 +19,6 @@ class Application < Rails::Application
     # -- all .rb files in that directory are automatically loaded after loading
     # the framework and any gems in your application.
 
-    # Use Sidekiq as ActiveJob backend
-    config.active_job.queue_adapter = :sidekiq
-
     # Configure generators, see: http://guides.rubyonrails.org/generators.html
     config.generators do |g|
       # Create appropriate tests in spec/ not test/

diff --git a/config/initializers/sidekiq.rb b/config/initializers/sidekiq.rb
@@ -5,7 +5,7 @@
 #
 # Client Size = Puma Workers * (Puma Threads / 2) * Heroku Web Dynos
 #
-# Server Size = (Redis Connection Limit - Client Size - 2) / Heroku Job Dynos
+# Server Size = (Redis Connection Limit - Client Size - 2) / Heroku Worker Dynos
 # Server Size is set in sidekiq.yml in concurrency setting.
 # Server size is concurrency + 2.