This seems cool but maybe not for a production setting requiring concurrency? I just signed up on PAYG which offers 3 concurrent sprites. I only see an option to upgrade to 10 concurrent sprites.
Without getting into Kurt's galaxy-brained take on the declining importance of "production" in a post-AI world, I'd say: yeah, run prod apps on Fly Machines, for more predictable performance, scaling, and pricing. Do exploratory computing --- "figuring out what you'd run on a Fly Machine" --- in Sprites.
Code and Let Live
191–195 of 195 posts
Re: Code and Let Live
#192Re: Code and Let Live
#193Re: Code and Let Live
#194Earlier quoted context omitted.
What I like about exe.dev is that you only need ssh to access it, is something like that under consideration for Sprites.dev? Additionally, is Tailscale/Wireguard connectivity something you'd consider?
Nope, re: SSH. Tailscale should already work on a Sprite. Everything we do at Fly.io is connected by WireGuard, so it's just a question of whether we want to expose that to users.
Re: Code and Let Live
#195fly.io is doing really good work. I've super enjoyed building our product on their platform. I love fly-replay combined with super fast start-up. I've been thinking a lot about how to run agents (and skills) securely while giving them a lot of powerful capabilities. I recently used their macaroons library to turn arbitrary API keys (e.g. for stripe's API) into macaroons. I route requests for an upstream host (like st…
Did you write up anything about this? Is this off the shelf behavior for Envoy or did you create this API yourself?
Here's the repo [1]. I modified it a bit to post publicly and remove the details of my setup within my tailnet/flycast network.