Feedback/requests from a Rails perspective: apps grouped with a shared deployment story, one-off apps/machines, and pipelines

[abe]

@Brad

Yeah, I love this about Heroku. Fly does it a bit differently with the processes directive in the fly.toml file and it’s kind of buried in the documentation. I recently documented it for Sidekiq at Sidekiq background workers · Fly Docs and App Configuration (fly.toml) · Fly Docs. There’s a few bugs that were just fixed with respect to multi-region scaling, so I’m going to update those docs.

Ah so I did miss something then. That’s funny, I actually remember scanning the “get your processes here” post but IIRC based on the “processes” name and the old post date I figured it was some kind of sugar for a supervisor process thing, which I didn’t want. Now actually reading more closely I see it does actually spin up different microVMs. Thanks!

One question about this - can I write something like this in my fly.toml and it’ll work?

[deploy]
  processes = ["jobdrain"]
  strategy = "rolling"

I need to use a rolling deploy strategy for my job drain because it uses a Postgres advisory lock and it can’t handle n>1 instances running (so canary deploys fail). Canary for the other stuff is fine though

@matthewford

Yes, but processes also have an issue where they do not work with autoscaling.

Ooh good to know