Is it feasible to dynamically deploy multiple machines from a single image, each with its own unique subdomain, using the Fly.io API? Our use case involves creating separate, accessible instances on-demand, potentially running concurrently, and then terminating them when no longer needed. Any guidan…

Yes, this is one of the use cases we intended with fly-replay. You run one app that decides where to route traffic, and then individual apps (or machines, see caveats) for backends. The request sequence would look like this: Request comes in to router app Router app checks subdomain against cache…

Here’s a small example: [image] How to route certain paths to another Fly app without a reverse proxy? Meet Fly-Replay Show & Tell We have an amazing feature called Fly-Replay that let anyone hosting apps on Fly teach our proxy how to reroute requests. Want t…

@kurt @lubien Thanks for the quick reply! I’d love to get your opinion before deciding which path to take. Let me provide more context about our use case: We’ve built a Zoom meeting bot with the following requirements: Each instance needs ~4GB RAM and 2 cores to run smoothly We need to boot a ma…

That bot architecture should work really well with the fly replay setup. We use fly-replay to establish long lived websocket connections and it’s really nice. You can actually hold a request in the router, create an app / machine, and then respond with fly-replay to it, if you’d like. You can crea…

Is it possible to make dynamic Multi-Machine Deployment with Unique Subdomains using Fly.io API?

Questions / Help

lubien July 17, 2024, 1:40pm 3

Here’s a small example: