Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Orphaned Flame Runner with Fly Blue/Green Deployment #49

Open
mikehostetler opened this issue Aug 7, 2024 · 0 comments
Open

Orphaned Flame Runner with Fly Blue/Green Deployment #49

mikehostetler opened this issue Aug 7, 2024 · 0 comments

Comments

@mikehostetler
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant