New feature: Scheduled machines

5

The best practice is to use the GraphQL APIs which are more mature (even if as inconsistent) over flyctl m commands.

I prefer flyctl and I have requested that Fly engs pls:

  1. Fix the existing flyctl m update <existing-machine-id> --dockerfile </path/to/file> --config </path/to/machines.toml> command.
  2. Support the --image switch like so, flyctl m update <existing-machine-id> --image <img> --config </path/to/machines.toml>.

It’d also be neat if flyctl m run <img> --name <existing-machine-name> --config </path/to/machines.toml> could deploy to an existing machine. But it doesn’t.

You could destroy machines and create new ones, if that’s what you prefer, or flyctl deploy --image <img> --now --strategy immediate --config </path/to/machines.toml> to deploy the img to all machine VMs of the app (as defined in machines.toml).

2 Likes