flyctl icon indicating copy to clipboard operation
flyctl copied to clipboard

Command line tools for fly.io services

Results 232 flyctl issues
Sort by recently updated
recently updated
newest added

When using `.env` files, it's very common to add single line certificates like so: ``` MY_CERT="-----BEGIN CERTIFICATE-----\nMIIFaz... etc ...FfLn\n-----END CERTIFICATE-----\n" ``` When using `fly secrets import` these vars get converted...

bug
good small task

### Change Summary Improve Django scanner. What and Why: Often the generated requirements.txt file contains only `-r requirements/dev.txt` or similar so there is no 'django' string in it. How: Add...

### Change Summary What and Why: This changes `fly domains disable` to `fly domains add`, which appears to be what the subcommand actually invokes. I noticed the discrepancy in this...

This commit prepares the codebase for a future implementation of xdg base dirs. Until now, the whole codebase assumed there was one "config dir" where anything flyctl-related went, even if...

**Describe the bug** I'd like to get flyctl into FreeBSD ports tree. The first step is to compile from source, which fails: ``` ### boot a FreeBSD 13.0-RELEASE image somewhere...

enhancement

*Please only report specific issues with `flyctl` behavior*. Anything like a support request for your application should go to https://community.fly.io. More people watch that space and can help you faster!...

bug

Add a new metric that records how long we spend pushing the docker image to our registry during `fly deploy`. This will help us understand regional variations and overall performance...

bug
good first issue
registry

### Change Summary What and Why: This solves two problems. 1. Users got annoyed that we picked Personal by default. This is totally understandable - we can pick reasonable default...

**Describe the bug** If all machines for an app are down, doing a `fly deploy` will not start new machines. This can be desireable behavior, but it could also be...

bug

The `--restart` flag for `fly m run` has `on-fail` as one of the options, but this should really be `on-failure` like it is in the Machines API and Docker's restart...

bug
good small task
ux
good first issue