“Yes. Fly.io Volumes can be attached to background-worker Machines, including workers defined as a process group in fly.toml.”
“Yes. Fly.io Volumes can be attached to background-worker Machines, including workers defined as a process group in fly.toml.”
“The data survives redeploys and Machine restarts.”
“Fly provides automatic volume snapshots by default, with five days of retention on new volumes.”
“The important caveat is that a Fly Volume is local, single-Machine storage, not a replicated network disk.”
“One Volume can only be attached to one Machine at a time, and Fly doesn't automatically replicate its contents.”
“Fly explicitly says volumes don't replicate across regions.”
“One subtle point: persistent doesn't mean highly durable/HA.”
