Open mattbnz opened 3 months ago
Hi @mattbnz I have faced multiple issues in the benchmarks and tests that I had to retract it, I am weighing out some options and would like your input:
auto_run: false
and require explicit running (e.g. in an initializer)auto_run_without_a_server: false
3 seems like the most reasonable to me, given that an initializer can be created with the current generator and the experience remains largely the same without running in console surprises
Thoughts? other options?
Option 3 definitely seems the most attractive of those options, and is in-line with my experiences with other job queues which usually have to be explicitly started.
Sorry for not thinking about the test/benchmark use-cases up front, seems blatantly obvious in hindsight :)
Do you have a plan for how to do option 3 already, or would you welcome a PR with some thoughts?
Thanks.
Happy to accept a PR
PR#99 merged a feature to prevent workers from running in the Rails console, but that was then disabled in later commits 0902676 and d191fb3 without much detail.
This bug is to track getting some details on what a "better solution" might look like - aka what was the issue encountered that required the feature being disabled again, and then the fix.
I'm happy to do some more work on this, but need details on what you'd like to see as the behaviour here.