Question: How does fly's proxy not send traffic to flame instances?

Open
#84 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Tech stack
elixir
Domain
cloud, infrastructure

Research direction

Start with the linked Flycast documentation and the issue's reverse-proxy and Flame setup. Investigate how Fly routes traffic to machines and whether Flame-created machines can be excluded or identified through configuration. Done means documenting the routing behavior, any required configuration, and whether this deployment pattern is supported.

Written by the indexing model from the issue text.

Description

This could be a question we need to ask to the Fly support team, but I'm assuming that the person/people working on this might know the answer.

Scenario:

We have a phoenix application that uses flame to spin up dynamic machines to process CPU intensive tasks. This app isn't exposed to the internet directly. We have another fly application that acts as a reverse proxy and proxies traffic to this phoenix application amongst others. We use the flycast address (described here). My understanding that this utilizes fly's internal proxy that will handle load balancing between machines, dynamically spinning up sleeping machines and such.

The question:

How does fly distinguish between normal machines and flame machines when determining where to send traffic? Is there some configuration on the fly side or flame side to prevent that proxy from proxying traffic to the flame machines?

I've gone through fly support to try and get this question answered, but they didn't seem super interested in digging into it with me and seemed to write it off as doing unsupported things. If running flame this way is unsupported, that would also be good to know.

Dominant language
Elixir
Stars
1.2k
Forks
68
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from phoenixframework/flame

All issues in phoenixframework/flame

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.