- Home
- Skills
- DevOps & Cloud
- Fly.io Config Check
More screenshots
Works with the AI Agents you already use
Fly.io Config Check
Check fly.toml before you deploy to Fly.io: secrets in [env] and build args, databases on public ports, statics that serve your source, HTTPS not forced, missing health checks, port mismatches and settings Fly rejects.
$5
Fly.io Config Check
Example session with this skill installed
Check this project with fly-io-config-check.
- Read your context and instructions
- Compiled the fly io config
$ python3 scripts/check_fly.py examples/risky
BLOCK fly.toml:9 F01 SECRET_IN_FLY_TOML
SENTRY_AUTH_TOKEN = "<redacted>"
Why: A password, token, private key or connection string with a password is written in fly.toml ([env], [build.args], a check header, a process, release or console command, or a [[files]] raw_value). fly.toml is committed with the code, so everyone who can read the repository can use the secret, and build arguments can stay in the image's history.
Safer: Store it with fly secrets set NAME=value (Fly keeps it encrypted and gives it to the Machines as an environment variable), use fly deploy --build-secret for build-time secrets and secret_name in [[files]], then change the secret that was committed.
BLOCK fly.toml:19 F01 SECRET_IN_FLY_TOML
BLOCK fly.toml:32 F02 DATABASE_PORT_PUBLIC_PLAINTEXT
BLOCK fly.toml:42 F03 STATICS_SERVE_APP_FOLDER
REVIEW cache/fly.toml:6 F14 IMAGE_NOT_PINNED
REVIEW cache/fly.toml:12 F13 NO_HEALTH_CHECKS
REVIEW cache/fly.toml:13 F12 DATABASE_OR_SSH_PORT_EXPOSED
REVIEW cache/fly.toml:15 F16 AUTO_STOP_ON_DATABASE
REVIEW docs/fly.toml:18 F20 STATICS_WEB_ROOT_HOLDS_REPO
REVIEW fly.toml:12 F17 RELEASE_COMMAND_NEEDS_VOLUME
REVIEW fly.toml:13 F18 SETTING_FLY_REJECTS_OR_IGNORES
REVIEW fly.toml:17 F15 APP_PORT_MISMATCH
REVIEW fly.toml:20 F19 DEFAULT_SECRET_VALUE
REVIEW fly.toml:22 F13 NO_HEALTH_CHECKS
REVIEW fly.toml:24 F11 HTTPS_NOT_FORCED
REVIEW fly.toml:25 F18 SETTING_FLY_REJECTS_OR_IGNORES
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 3 files, 3 with fly.toml content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
A SESSION_SECRET in [env] goes to everyone who can read the repository, a [[services]] block for Redis gives the cache a public address on the first deploy, and a [[statics]] entry pointing at /app serves your .env and source files to anyone who asks for them. This skill finds those and the other Fly.io config mistakes below before you deploy, and tells you how to fix each one.
Your agent runs a scanner on fly.toml and its variants (fly.staging.toml, fly.production.toml) and on the Dockerfile fly deploy builds for it (its WORKDIR, COPY . ., ENV PORT and start command). It reads the TOML with a line number for every key, knows the defaults of [http_service] and [[services]] (internal port 8080, ports 80 and 443), the tls and pg_tls handlers and process groups, skips placeholders, ${...} references and public-by-design keys, and never runs flyctl, Docker or your app. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- F01: passwords, tokens, keys and connection strings with a password written in [env], [build.args], process, release or console commands (also a flag and its value in separate array items), health check headers or a [[files]] raw_value
- F02: a database or cache port (PostgreSQL, MySQL, Redis, MongoDB and others) served as plain TCP with no tls or pg_tls handler, unless a comment marks the app as private (# flycast only)
- F03: [[statics]] that serve / or a system folder, or the folder the Dockerfile copies the whole project into
REVIEW
- F11: [http_service] or an http port without force_https = true
- F12: SSH, a database port with TLS at the proxy, or a plain database port in an app marked as private
- F13: a public service with no health check of any kind
- F14: [build] image or a machine_checks image with no tag or on latest
- F15: an internal_port that differs from [env] PORT or HTTP_PORT, the Dockerfile's ENV PORT or a --port/--bind flag in the start command, or an app bound to localhost
- F16: auto_stop_machines on in a database or cache app that has a volume
- F17: a release_command that needs the volume (release commands run without volumes), such as a SQLite migration
- F18: settings Fly rejects or ignores: canary or bluegreen with volumes, bluegreen without a health check, force_https on a non-http port, a volume mounted at /, FLY_ variables, suspend with swap or more than 2 GB (memory, memory_mb or the size preset), and unknown process groups
- F19: a secret-named [env] or [build.args] variable set to a default word such as password, changeme or admin
- F20: [[statics]] on an nginx, Caddy or httpd web root that the Dockerfile fills with the whole build context
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official Fly.io documentation link for each rule
- A risky and a safe example project (a web app, a Redis app and a static docs site, each with fly.toml, plus their Dockerfiles), and the real report the scanner produces on the risky one
Limits It reads fly.toml and the Dockerfile as written. It cannot see your app's IP addresses, values set with fly secrets, or changes made with fly scale or the Machines API, so the database and SSH port rules assume Fly's default of public addresses for apps with services (a "# flycast only" comment marks a private app), and F19 cannot tell whether a Fly secret overrides the default value. The fly launch template of most frameworks writes no health check, so expect F13 there. Ports chosen in code or in a Procfile are not followed, and Dockerfile security itself is not checked. NOT FLAGGED is not a guarantee.
Static check of fly.toml and Dockerfile text. The app's IP addresses, Fly secrets and settings changed outside fly.toml are not known. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Requires
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert secrets (not-a-real-...) and a default password for the scanner to find. Nothing in it is run.