Preview: Deploying applications on Machines with flyctl

5

A few disparities between flyctl deploy and flyctl m run:

  1. Creating a new machine with flyctl m run --c <path/to/config> doesn’t respect primary_region set in the config and instead deploys to the region the wireguard peer is connected to (usually, the nearest one). flyctl deploy -c ... does respect the primary_region directive

  2. Also, flyctl m run -c </path/to/config> doesn’t seem to use any [env] vars from the config (as before, flyctl deploy -c ... does).

Incorrect behaviour with flyctl deploy -c ...ing a machine.

  1. Even though [services] section exists with ports and handlers defined in my config, flyctl deploy -c ... did not allocate a public-ip (neither v4 nor v6) address; but the documentation says otherwise.