Orphaned Flame Runner with Fly Blue/Green Deployment
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- elixir
- Domain
- cloud, infrastructure
Research direction
Start with the FLAME.Pool configuration using the FlyBackend and the fly.toml [deploy] strategy set to bluegreen. Investigate the deployment and termination lifecycle; done means the persistent Flame machine is terminated during each blue/green deploy rather than orphaned.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Elixir
- Stars
- 1.2k
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from phoenixframework/flame
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
phoenixframework/flame#86 · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
phoenixframework/flame#84 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
phoenixframework/flame#75 · 2 comments ·
-
Clean up code_sync tmp files on terminator shutdownMay be free again @chrismccord claimed this 676 days ago, and no pull request is open. Open
phoenixframework/flame#70 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
phoenixframework/flame#66 · 1 comment ·
All issues in phoenixframework/flame
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
carverauto/serviceradar#5264 ·
Maintainers usually reply within 1 day
-
Handle short ciphertext in AES-GCM Decrypt instead of panickingPossibly taken @pamod-madubashana claimed this 3 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
semaphoreio/semaphore#1305 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QuinnWilton/argus#5 · 1 comment ·
-
help-wanted L: docker L: elm L: github:actions L: helm L: ruby:bundler
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
dependabot/dependabot-core#16425 ·
Maintainers usually reply within 2 days
-
Cainophile EXIT handler crashes on its own password redaction and logs the DB password in clear textOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days