Live data from Hacker News

Code and Let Live

fly.io

191–195 of 195 posts

Re: Code and Let Live

#191
post #99

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.

The last few hours were a roller coaster after spending my weekend trying to build something Sprites-like on Fly Machines to power a feature in a larger project, then coming across this (great, I don't need to build it!) to realizing this is a seemingly a consumer product and I haven't been saved from an awful slog.

Re: Code and Let Live

#194

Earlier 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.

Tailscale definitely had issues for me, unless I used user-mode networking and even then it was iffy. I should add that it also auto-signed me up for a trial of Fly.io itself, which is useless to me now but might've come in handy later.

Re: Code and Let Live

#195
post #13

fly.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?

sorry for the delayed response. I ended posting on this [0] thread where they (Formal) are doing something similar.

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.

[0] https://news.ycombinator.com/item?id=46605155

[1] https://github.com/dtkav/agent-creds

Post reply on HN