--- next_cursor: eyJzY29yZSI6MCwic2VxIjoxMTI0LCJzaW5jZSI6bnVsbCwidG9vbCI6ImZseWN0bCIsInYiOjF9 has_more: true next: https://sincecutoff.com/v1/changes.md?tool=flyctl&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxMTI0LCJzaW5jZSI6bnVsbCwidG9vbCI6ImZseWN0bCIsInYiOjF9 items: 10 --- # sincecutoff.com changes: flyctl ## flyctl mpg attach tracks app attachments to MPG clusters (flyctl, 2026-01-08) Published 2026-10-16 - slug: flyctl-mpg-attach-tracks-app-attachments-to-mpg-clusters-e56e363cb016 - score: 0.95 How to use it: When connecting an app to a Managed Postgres cluster, run `fly mpg attach` to add a connection secret and create the attachment record. Use `fly mpg attach list` to verify attached app names; use `fly mpg detach` to remove the attachment while retaining the secret. Examples: ``` fly mpg attach --app ``` ``` fly mpg detach --app ``` - why_it_matters: When connecting an app to a managed Postgres cluster, attach the cluster to the app and verify its attachments. - before: Previously `mpg attach` created a secret and deployed; it did not create an explicit database connection record between the cluster and app. - sources: , , , - gotchas: "Version: v0.4.2"; ": Managed Postgres cluster ID; when omitted, the command prompts for a cluster."; "--app (required): Select the app to attach or detach; the command requires an app name."; "--variable-name : Secret environment variable name to add to the app; defaults to `DATABASE_URL`."; "--database, -d : Database to connect to; when omitted, an interactive session prompts for selection."; "--username, -u : Database user to connect as; when omitted, an interactive session prompts for selection."; "Prerequisite: A Fly.io authenticated session is required."; "Prerequisite: The app and cluster must belong to the same organization."; "`mpg detach` removes the attachment but does not remove the secret." ## flyctl machine supports --swap-size (flyctl, 2026-02-10) Published 2026-10-16 - slug: flyctl-machine-supports-swap-size-fab655d9bef5 - score: 0.93 How to use it: When configuring a machine with `flyctl` v0.4.9, set a positive swap size with `fly machine run --swap-size `. The size accepts a number in MB or a human-readable value such as `512mb` or `1gb`. Examples: ``` fly machine run --swap-size ``` - why_it_matters: Set the swap size when configuring a machine. - sources: , - gotchas: "Version: v0.4.9"; "--swap-size : Swap size in MB; accepts a plain number in MB or a human-readable size such as `512mb` or `1gb`. If specified, it must be greater than zero."; " (required): Image or path argument for `machine run`." ## flyctl certificates use the Machines API with custom certificate uploads and domain ownership verification (flyctl, 2026-02-12) Published 2026-10-16 - slug: flyctl-certificates-use-the-machines-api-with-custom-certificate-uploads-and-dom-8f01b1631cf2 - score: 0.95 How to use it: When managing an app certificate, use `fly certs` commands. Import a custom PEM certificate and key with `import`; use `setup` for DNS instructions and `check` after adding the ownership record. Examples: ``` fly certs import -a --fullchain --private-key ``` ``` fly certs setup -a ``` ``` fly certs check -a ``` - why_it_matters: Manage certificates for an application, including uploading a custom certificate or verifying domain ownership. - sources: , , - gotchas: "Version: v0.4.11"; " (required): Hostname for the certificate."; "-a, --app : Application name; the command requires an app name, which may come from app configuration instead."; "--fullchain (required): Path to the certificate chain file in PEM format."; "--private-key (required): Path to the private key file in PEM format."; "Prerequisite: The certificate import command requires an authenticated Fly session and an app name."; "Prerequisite: Provide the certificate chain and private key in PEM format. Domain ownership must be verified through DNS before the imported certificate becomes active."; "Certificates are primarily serviced through the Machines API rather than GraphQL."; "The DNS entry can verify domain ownership in certain circumstances." ## flyctl machine wait waits for a machine state (flyctl, 2026-03-09) Published 2026-10-16 - slug: flyctl-machine-wait-waits-for-a-machine-state-b68c8dfedd8f - score: 0.96 How to use it: When a CLI workflow needs to wait for a Fly Machine to reach a state, run `fly machine wait `; it waits for `settled` by default. Use `--state ` to select a target and `--wait-timeout ` to set the timeout. Examples: ``` fly machine wait ``` ``` fly machine wait --state ``` ``` fly machine wait --state --wait-timeout ``` - why_it_matters: Wait for a machine to reach a target state or settle during a CLI workflow. - sources: , , - gotchas: "Version: v0.4.20"; "machine-id: Optional positional machine ID; command allows zero or one argument and selects a machine when omitted."; "--state: Machine state to wait for; defaults to `settled`."; "--wait-timeout: Duration to wait for the machine to reach the requested state; defaults to 5 minutes. Shorthand: `-w`."; "Prerequisite: Requires an authenticated flyctl session." ## flyctl machine run and update accept --vm-max-memory (flyctl, 2026-03-23) Published 2026-10-16 - slug: flyctl-machine-run-and-update-accept-vm-max-memory-1bcd5e429b48 - score: 0.92 How to use it: When running a new machine or updating an existing one, pass `--vm-max-memory ` to set its maximum memory in MB. The v0.4.27 source documents the flag as hidden and rejects zero or invalid sizes. Examples: ``` fly machine run --vm-max-memory --app ``` ``` fly machine update --vm-max-memory --app ``` - why_it_matters: Set a machine's maximum memory while running or updating it. - sources: , , , - gotchas: "Version: v0.4.27"; "--vm-max-memory : Maximum memory, in megabytes, allowed for the VM. Parsed as a size; zero is rejected. The flag is hidden and has no alias."; " (required): Image or Dockerfile path argument for `machine run`."; " (required): Machine identifier argument for `machine update`."; "--app : Application name; the run command source lists the app flag."; "Docs conflict: The run command source page is on master, newer than v0.4.27; it is used only for the `` argument, not for the new flag behavior." ## flyctl machine run and update add --cachedrive-size (flyctl, 2026-04-08) Published 2026-10-16 - slug: flyctl-machine-run-and-update-add-cachedrive-size-dc82027c76bb - score: 0.90 How to use it: When setting a cache drive size while running or updating a machine, pass `--cachedrive-size ` to `fly machine run` or `fly machine update`. Use a plain number in MB or a human-readable size; `0` disables the cache drive. Examples: ``` fly machine run --cachedrive-size ``` ``` fly machine update --cachedrive-size ``` - why_it_matters: Set a cached drive size when running or updating a machine. - sources: , , - gotchas: "Version: v0.4.32"; "--cachedrive-size : Cache drive size in MB; accepts a plain number in MB or a human-readable size such as `512mb` or `10gb`. Set to `0` to disable."; " (required): Image argument for `run`."; ": Machine ID argument for `update`; the command definition allows it to be omitted."; "Prerequisite: The command requires a flyctl session." ## flyctl tokens create readonly adds an organization flag (flyctl, 2026-04-30) Published 2026-10-16 - slug: flyctl-tokens-create-readonly-adds-an-organization-flag-3a477b9f6afa - score: 0.91 How to use it: When creating a read-only token for an organization, run `flyctl tokens create readonly -o `. Examples: ``` flyctl tokens create readonly -o ``` - why_it_matters: Create a read-only token scoped to an organization. - sources: - gotchas: "Version: v0.4.44"; "-o, --org (required): Specifies the organization for `tokens create readonly`." ## fly mpg database extensions list, enable, and disable commands (flyctl, 2026-07-08) Published 2026-10-16 - slug: fly-mpg-database-extensions-list-enable-and-disable-commands-898ca75be6a3 - score: 0.98 How to use it: When managing extensions on an MPG cluster from a non-interactive workflow, use the documented list, enable, or disable command for the target database. The current official CLI docs use `databases` in the command path; the card and release note use `database`, so verify the installed CLI’s syntax before running it. Examples: ``` fly mpg databases extensions list [flags] ``` ``` fly mpg databases extensions enable --cluster --database [--schema ] [--create-schema] ``` ``` fly mpg databases extensions disable --cluster --database [--force] ``` - why_it_matters: Manage extensions on a Managed Postgres cluster from a non-interactive workflow such as CI. - before: The release note says extensions could previously only be enabled via the dashboard. - sources: , , , , - gotchas: "Version: v0.4.68"; " (required): Target cluster ID for `list`."; "--database, -d: Target database within the cluster; listed as an option for `list`."; "--json, -j: Output list results as JSON."; " (required): Postgres extension to enable or disable."; "--cluster, -c (required): Target cluster ID for enable or disable."; "--database, -d (required): Target database within the cluster for enable or disable."; "--schema: Schema in which to create the extension; default is `public`."; "--create-schema: Create the schema if it does not exist."; "--force: Drop dependent objects as well (`CASCADE`) when disabling."; "--access-token, -t: Fly API access token global option."; "Prerequisite: Use a flyctl version that includes the commands; release v0.4.68 added them."; "Prerequisite: For enable or disable, authenticate with a Fly API access token; docs list `--access-token` as a global option."; "Applies to new V2 clusters and existing V1 clusters."; "Docs conflict: Card and release note use `fly mpg database extensions ...`; current official CLI docs document `fly mpg databases extensions ...` (plural). The official v0.4.68 source is at https://github.com/superfly/flyctl/blob/v0.4.68/internal/command/mpg/extensions.go, but the retrieved source page did not expose command usage text." ## fly logs adds machine selection (flyctl, 2026-07-22) Published 2026-10-16 - slug: fly-logs-adds-machine-selection-3cf3ff2be05a - score: 0.95 How to use it: When debugging an app with multiple Machines, run `fly logs -m ` to filter logs to one Machine, or `fly logs -s` to select one interactively. The command requires an authenticated Fly session and an app name. Examples: ``` fly logs -m ``` ``` fly logs -s ``` - why_it_matters: Narrow log inspection to one Machine while debugging an app with multiple Machines. - before: List Machines and copy a Machine ID before narrowing logs to one Machine. - sources: , , - gotchas: "Version: v0.4.74"; "-m, --machine : Filter logs by Machine ID. Alias: `--instance` / `-i`."; "-s, --select: Select a Machine from a list; cannot be used with `--machine`."; "Prerequisite: Requires an authenticated Fly session and an app name; the app can be determined from `fly.toml` or supplied with the app flag."; "The `-s` selection is interactive."; "The `--instance/-i` alias is hidden but still works." ## flyctl [build] accepts Dockerfile URLs (flyctl, 2026-07-27) Published 2026-10-16 - slug: flyctl-build-accepts-dockerfile-urls-b8fe9c6e325f - score: 0.97 How to use it: When `[build].dockerfile` is hosted remotely, set it to the Dockerfile URL and deploy from the repository root; flyctl keeps the project root as the default build context. The URL is downloaded when a Dockerfile builder needs it and the same copy is reused throughout the deploy. Examples: ``` [build] dockerfile = "" flyctl deploy ``` - why_it_matters: Deploy a repository whose `[build] dockerfile` is hosted remotely while retaining the local build context. - before: Set `[build] dockerfile` to a local path for Dockerfile builds. - sources: , , , - gotchas: "Version: v0.4.75"; "[build].dockerfile: Accepts a relative Dockerfile path or a URL; defaults to `Dockerfile` in the application root. It does not change the Docker context, which defaults to the project root."; "Prerequisite: Install flyctl and sign in to a Fly account before deploying."; "The URL is fetched only when a Dockerfile builder needs it."; "Downloads have a 30 second timeout and a 10 MiB limit."; "The downloaded file is stored in a private temporary directory that is cleaned up before deploy continues."; "Redirects drop query-bearing Referer headers and refuse HTTPS-to-HTTP downgrades."; "Local Dockerfiles and non-Dockerfile builds are unchanged." Next: https://sincecutoff.com/v1/changes.md?tool=flyctl&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxMTI0LCJzaW5jZSI6bnVsbCwidG9vbCI6ImZseWN0bCIsInYiOjF9 Save `next_cursor`; next visit, pass it to get only what was published since.