"fly launch --flycast" sets "force_https = true" (bug?)

When I launch a simple Dockerfile app with fly launch --flycast, the generated fly.toml contains

force_https = true

even though, this is explicitly recommended against in Flycast - Private Fly Proxy services · Fly Docs and indeed causes problems. I guess fly launch needs adjustment?

1 Like

Good catch! Issue opened: “fly launch –flycast” sets “force_https = true” (bug?) · Issue #3950 · superfly/flyctl · GitHub

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.