# fetch vm-ids
fly m list -a <machine-app-name>
# fetch config
fly m status <vm-id> -d -a <machine-app-name>
…should accurately blurt out the config
specific to that machine-vm. Each machine-vm can be run with a different config
and so you’d not find a VM’s config values in the app’s overall config
(if that makes sense…).
Also: flyctl deploy does not honour all entries in config for machine apps - #2 by eli
Edit: Btw, I don’t think Fly’s edge proxy can load balance (using services.concurrency
) among multiple machines (of an app) in the same region, yet (but will eventually, as Machine’s where Fly is betting its resources on): Preview: Postgres on Machines ( Fly Apps V2 ) - #2 by ignoramous (which unfortunately results in at least 2x the costs for us than it should).