Note that you may only mount one volume per VM, currently (so, only one array entry). We’ll get this into the docs!
Support for fly.toml has just been released, so it’s pretty raw. fly.toml is not supported for creating machines with fly machine run, but once an app has machines, you can create a new fly.toml for it and run fly deploy against it like a standard Fly app. The deployment will override the settings on the machines, so I wouldn’t use this yet if you plan to attach volumes.
It’s not possible yet, but the plan is most likely to have a single API for all operations. We’re not immediately doing this because we want to think hard about the correct DX here. For example, volumes might just be created along with VMs. OR, IPs automatically allocated when a public service is detected (like in the old platform).
It seems like there is an issue when I attach a volume to my machine. The machine starts but is never ready. Are you on Discord or Slack @jsierles? It would be simpler to share what I’m doing. I’m jgoux#5970 on Discord