flame icon indicating copy to clipboard operation
flame copied to clipboard

Orphaned Flame Runner with Fly Blue/Green Deployment

Open mikehostetler opened this issue 6 months ago • 0 comments

I've configured my Flame.Pool to use the FlyBackend and keep a single machine always running in my supervision tree:

        {
          FLAME.Pool,
          name: MyApp.FlameRunner,
          min: 1,
          max: 10,
          max_concurrency: 10,
          idle_shutdown_after: 30_000
        },

My fly.toml file is configured to utilize the bluegreen deployment strategy:

[deploy]
strategy = "bluegreen"

On each deploy, the Flame machine continues to run and is not terminated in the deploy process.

I'm sure there's a straightforward solution utilizing proper termination events - but I wanted to catalog this issue here for others reference. I will post updates as I work towards my solution.

mikehostetler avatar Aug 07 '24 14:08 mikehostetler