Phil Pirozhkov

Probably ``` class ActiveRecord::Base def self.replicate_id true end end ``` for all, and for a specific model: ``` class Article < ActiveRecord::Base replicate_id true end ```

Ping

I haven't yet, but since you support the idea, I'll tackle it. For the implementation, I think of something very similar to [this](https://github.com/rspec/rspec-rails/blob/a78519850c8c8c3cf86319b2cc0b214bf16a6372/lib/rspec/rails/matchers/active_job.rb#L233).

Released as https://github.com/pirj/rspec-enqueue_sidekiq_job https://rubygems.org/gems/rspec-enqueue_sidekiq_job I've closed the PR. Please feel free to close the ticket as well.

0.2.0 at least!

I would prefer starting thin in userspace, e.g. `systemctl enable --user thin-marmite`. This will allow running several thin servers on a single machine under different users, and there's no chance...

@pothibo Makes sense

I suggest file format strongly depends on how gems are bundled and is rvm installed. I don't see any need in rvm in production, and install gems in the following...

Wondering if this will work for you: ```ruby FactoryBot.define do Response = Trav3::Response factory :response do body { { a: :b, c: :d }.to_json } end end ```

My rule of thumb is to sanitize anything that can be user-provided (including when it's coming from the database, or uploaded/fetched files, not just HTTP params), and only allow it...