good_job | Multithreaded , Postgres-based , Active Job backend | Application Framework library

Add good_job to your application’s Gemfile:.
Add good_job to your application’s Gemfile: ```ruby gem 'good_job' ```
Install the gem: ```bash bundle install ```
Run the GoodJob install generator. This will generate a database migration to create a table for GoodJob’s job records: ```bash bin/rails g good_job:install ``` Run the migration: ```bash bin/rails db:migrate ``` Optional: If using Rails' multiple databases with the `migrations_paths` configuration option, use the `--database` option: ```bash bin/rails g good_job:install --database animals bin/rails db:migrate:animals ```
Configure the ActiveJob adapter: ```ruby # config/application.rb or config/environments/{RAILS_ENV}.rb config.active_job.queue_adapter = :good_job ```
Inside of your application, queue your job 🎉: ```ruby YourJob.perform_later ``` GoodJob supports all ActiveJob features: ```ruby YourJob.set(queue: :some_queue, wait: 5.minutes, priority: 10).perform_later ```
In development, GoodJob executes jobs immediately. In production, GoodJob provides different options: By default, GoodJob separates job enqueuing from job execution so that jobs can be scaled independently of the web server. Use the GoodJob command-line tool to execute jobs: ```bash bundle exec good_job start ``` Ideally the command-line tool should be run on a separate machine or container from the web process. For example, on Heroku: ```Procfile web: rails server worker: bundle exec good_job start ``` The command-line tool supports a variety of options, see the reference below for command-line configuration. GoodJob can also be configured to execute jobs within the web server process to save on resources. This is useful for low-workloads when economy is paramount. ```bash GOOD_JOB_EXECUTION_MODE=async rails server ``` Additional configuration is likely necessary, see the reference below for configuration.