sidekiq-enqueuer doesn't work when having client separated from server.

[thegreyfellow]

Hi, first of all thanks for your work on bringing this to sidekiq, it's pretty much awesome. unfortuantely it didn't work for the setup I'm using.

• A rails app where the client is defined and where I use Sidekiq::Client api to push jobs to redis.
• A pure ruby worker where the server is running and dockerized and is deployed to many separate VMs.

I would love to see this added to this middleware, even hearing any suggestions from you or anyone to start a pull request on this would be very helpful.

Thanks, what are your thoughts?

[salmanasiddiqui]

is the codebase same for client and worker? As far as I can tell, this gem looks for loaded Sidekiq::Workers classes, if there are none then you won't be able to queue any job from GUI as you won't see any job.

so whatever script is running sidekiq web, you need to ensure that workers are required/loaded before running sidekiq web.