I’ve got the usual
worker process types in my
fly.toml. For context, I am using sidekiq and I’d like to assign specific instances to consume specific queues.
I know this feature is preview and I’m super thankful for that. It seems that I should be falling back to the
worker process types. I wonder whether there’s anyone out there who has successfully assigned instances to specific queues, since the
config/sidekiq.yml would apply the same config to any instance of the
I’ve successfully deployed them, but it see a couple of issues:
- They seem to spin up in a different region (DFW instead of LAX) - the app has LAX as a primary region, SEA and SJC in the backup region. This happened once, at least the first time I deployed the config change below.
- Secrets aren’t being picked up (noticed because the sidekiq worker tried to connect to the default
This leads to workers not spinning up obvs.
My config is something along the lines of this piece of my
[processes] web = "bundle exec rails server -b [::] -p 8080" download_worker = "sidekiq -c 1 -q downloads" import_worker= "sidekiq -c 5 -q imports" notifications_worker="sidekiq -c 1 -q notifications"
Any help would be very appreciated!