wake-on-schedule instead of wake-on-request?

[ignoramous]

fly deploy should just work and update all Machines of the app (ref). If not, there’s fly m update:

New feature: Scheduled machines

So, the PR (linked above) was merged (and hopefully, isn’t reverted before the next release). This command should build and deploy a new image with schedule intact: # alternatively, specify the --image switch if using a prebuilt fly m update <machine-id> --dockerfile </path/to/file> -a <app-name> I’ll send another PR to fix fly deploy wiping out schedule, in a bit.