michaeldwan

5 ms·

1.
by michaeldwan 5mo ago
you're spot on. I use both Claude Code + OpenCode with many different models and friction is minimal as long as I'm deliberate about it. Hell, even symlinking AGENTS.md to CLAUDE.md is like 80% there. It's just portability v
2.
by michaeldwan 5mo ago
I credit containerization, k8s, and terraform for preventing vendor lock in. Compute like EC2 or GCE are effectively interoperable. Ditto for managed services for k8s or Postgres. The new products Anthropic is shipping is more like Lambda.
3.
by michaeldwan 3y ago
Get out of here with this nonsense. We tell people when we’re a bad option all the time. Do you really think we have a desire (or time) to punish somebody for doing the same? Also, here’s the long forgotten badge, still with 3 people… htt
4.
by michaeldwan 3y ago
My point was that the app-not-working category is used in conjunction with support/our team getting involved. I assume this is what Sam meant by "flagged it internally", which was followed by investigation, then a post. I don
5.
by michaeldwan 3y ago
That category was added after one of our support folks replied, likely for tracking. I don't know why it's private. They may not even know this category is private. Hiding negative shit wasn't a deliberate decision... we&#x27
6.
by michaeldwan 3y ago
I don't know why the app-not-working category effectively delists threads, but until we find out, I just removed it so this thread is public again.
7.
by michaeldwan 3y ago
As an employee that would be a catastrophic outcome.
8.
by michaeldwan 4y ago
Docker (or rather OCI) is our first class citizen. The launchers for phoenix/rails/etc just generate dockerfiles and config by inspecting source code.
9.
Fly.io (YC W20) Is Hiring Ops Engineers(fly.io)
1 points by michaeldwan 4y ago
10.
by michaeldwan 4y ago
This is really cool! I don't use discord much, how much effort would a Slack bot version be?
11.
by michaeldwan 4y ago
We do hire entry level people, in fact we're wrapping up our first cohort of interns right now. Exclusively hiring experienced dudes from the tech bubble is a failure mode in the long run. We're invested in hiring folks with diver
12.
by michaeldwan 4y ago
This is for employees only. We don't collect more than necessary for customers, and if we did we sure as hell wouldn't be sending it to Google.
13.
by michaeldwan 4y ago
Ah!!! Thanks for pointing that out, we'll take it down.
14.
by michaeldwan 4y ago
That’s an old api we need to sunset. How did you stumble on it?
15.
by michaeldwan 4y ago
What rest api is that? If it’s not the machines api it’s in graphql at api.fly.io/graphql.
16.
by michaeldwan 4y ago
Ah! I've had volumes on the top of my mind all week... Firecracker supports snapshots in a dev preview but we're not using it yet. We can't really do anything like that on Nomad, which is one of the many reasons we're ke
17.
by michaeldwan 4y ago
If you mean moving (or copying) VMs to another region/host, sorta. Stateless compute is easy; our apps platform (orchestrated by Nomad) already does it. Volumes complicate things because they live on a specific host, and moving volumes
18.
by michaeldwan 4y ago
It already has it [1]. Native litestream that RPC's to the primary sounds interesting though! [1] https://github.com/phoenixframework/phoenix/pull/4268
19.
by michaeldwan 4y ago
We're not shying away from "boring" stuff at all. We just have a small team with bigger priorities that's spread too thin. There's a million things like resizable volumes we need to ship and we're aggressively
20.
by michaeldwan 4y ago
> there’s no obvious way to resize disks Yes, this sucks right now. Resizable disks is on our list, we just need somebody to spend a few days on it. Luckily we're hiring platform engineers [1] to work on fun problems like that. >
21.
Fly.io (YC W20) Is Hiring Platform Engineers(fly.io)
1 points by michaeldwan 4y ago
22.
by michaeldwan 5y ago
Node, Ruby, and Python come to mind. Oddly enough the alpine versions of haproxy and nginx on Docker hub had issues too.
23.
by michaeldwan 5y ago
Failing in one AZ probably means they changed something with DNS servers for that region. We had a similar issue recently when we rolled out a new DNS server that returned longer SOA records which broke python's mysql driver in only so
24.
by michaeldwan 5y ago
I really want to like Alpine, but we (Fly.io) have seen so many DNS issues with customer images that we’re now recommending Ubuntu or Debian slim. The extra ~50mb is a worthwhile trade off to avoid hard to debug musl-libc issues. eg https:
25.
by michaeldwan 5y ago
You control which region your app and it’s volumes are in. Metrics, logs, and volume snapshots end up on servers in the USA. We haven’t addressed data residency for those platform services yet, but we might someday if there’s enough interes
26.
by michaeldwan 5y ago
We'll write about it when the time comes. To be fair, Nomad and Consul have served us well. Most of our troubles stem from abusing them in ways they weren't designed to handle.
27.
by michaeldwan 5y ago
As for autoscaling, our hands are tied as long as we're running on Nomad. Right now our autoscaler is nothing more than some ruby that loops over data from prometheus and changes counts in Nomad. It's slow and buggy, but worse we
28.
by michaeldwan 5y ago
It's unlikely we'll open source the Elixir app, most of it isn't that interesting. But extracting the machine code into an example app is a good idea! Until then, here's a prototype go proxy that launches suspended machi
29.
by michaeldwan 5y ago
The build executes untrusted code and temporarily authenticates with your fly.io and Heroku accounts, so we need a sandbox for isolation. Our Elixir app launches ephemeral VMs using our Machines API so it can offload that can of worms.
30.
by michaeldwan 5y ago
We use wireguard-go in our cli for connecting to vms over a private network. It is slower than wireguard in the kernel, but the convenience is hard to beat. Here's an overview https://fly.io/blog/ssh-and-user-mode-

More ›