fix: fix key error issue

Author: ramsayleung

app/jobs/telegram_background_worker_job.rb

@@ -10,15 +10,15 @@ class TelegramBackgroundWorkerJob < ApplicationJob
 
   def perform(args)
     Rails.logger.info "Performing telegram background job: #{args}"
-    action = args.fetch("action")
+    action = args.fetch(:action)
 
     case action
     when PostAction::BAN_USER
-      trained_message = args.fetch("trained_message")
+      trained_message = args.fetch(:trained_message)
       ban_user_in_group(trained_message: trained_message)
     when PostAction::DELETE_ALERT_MESSAGE
-      chat_id = args.fetch("chat_id")
-      message_id = args.fetch("message_id")
+      chat_id = args.fetch(:chat_id)
+      message_id = args.fetch(:message_id)
       delete_message(chat_id: chat_id, message_id: message_id)
     end
   end

config/deploy.yml

@@ -9,10 +9,10 @@ servers:
   web:
     hosts:
       - 192.168.1.188
-  # job:
-  #   hosts:
-  #     - 192.168.1.188
-  #   cmd: bin/jobs
+  job:
+    hosts:
+      - 192.168.1.188
+    cmd: bin/jobs
 
 # Enable SSL auto certification via Let's Encrypt and allow for multiple apps on a single web server.
 # Remove this section when using multiple web servers and ensure you terminate SSL at your load balancer.
@@ -36,10 +36,10 @@ registry:
 env:
   secret:
     - RAILS_MASTER_KEY
-  clear:
+  # clear:
     # Run the Solid Queue Supervisor inside the web server's Puma process to do jobs.
     # When you start using multiple servers, you should split out job processing to a dedicated machine.
-    SOLID_QUEUE_IN_PUMA: true
+    # SOLID_QUEUE_IN_PUMA: true
 
     # Set number of processes dedicated to Solid Queue (default: 1)
     # JOB_CONCURRENCY: 3