remove resque, use active_job instead

[orangewolf]

This can still be used with Resque, but can now also be used with DelayedJob, Sidekiq or whatever other job processor your Rails app is running. Note that Hyrax uses ActiveJob.

[orangewolf]

should have mentioned this the other night, but I'm open to making this an option if that's more desirable.

[cziaarm]

Possibly my own miss configuration elsewhere, but I have found that https://github.com/notch8/irus_analytics/blob/active_job_edition/lib/irus_analytics/irus_analytics_logger.rb#L39-L43 is "hiding" log messages a in a Rails log file when the messages are sent by the worker and Rails is otherwise logging to STDOUT

I stopped this by switching in

                       @@debug_logger ||= if Sidekiq.server?
                           Sidekiq::Logging.logger
                         else
                           Rails.logger
                         end

but that assumes that config.active_job.queue_adapter = :sidekiq and as this PR helps this gem be more generic, I don't want to suggest anything that makes it specific in a different way.... so just raising in case there's a better way to solve (if it is even a problem)

[orangewolf]

Possibly my own miss configuration elsewhere, but I have found that https://github.com/notch8/irus_analytics/blob/active_job_edition/lib/irus_analytics/irus_analytics_logger.rb#L39-L43 is "hiding" log messages a in a Rails log file when the messages are sent by the worker and Rails is otherwise logging to STDOUT

I stopped this by switching in

                       @@debug_logger ||= if Sidekiq.server?
                           Sidekiq::Logging.logger
                         else
                           Rails.logger
                         end

but that assumes that config.active_job.queue_adapter = :sidekiq and as this PR helps this gem be more generic, I don't want to suggest anything that makes it specific in a different way.... so just raising in case there's a better way to solve (if it is even a problem)

that seems to imply that Rails.logger is not set to stdout in whatever environment your background jobs are running under. Are you sure that RAILS_LOG_TO_STDOUT is set to true on your background worker?