Stick client to a specific worker

[dmitry]

Is there a way to a stick client via cookies or one specific header in the request to a specific worker?
Use case: I need to create a worker, where each of them is going to be bounded to a specific database (postgres, redis etc), and also VCR is going to be triggered remotely for a single spec. Going to be used for the cypress specs.

[dentarg]

Use single mode?

[dmitry]

@dentarg do you mean set 1 worker and 1 thread? Seems like that is the only solution due now, but in that case, I have to use different ports to follow the test runners to a different instance. Seems like going to follow this strategy for now.

[dentarg]

No, single mode is 0 workers:

puma/docs/deployment.md

Line 19 in 99ae85b

To run `puma` in single mode (i.e., as a development environment), set the

[dentarg]

Even if you could stick clients to specific workers, I don't think that can help you, as you can not make workers behave differently? Workers are always the same, serving your app. Am I missing something? Just make your app use a different database depending on some info in the request (query param perhaps)?