Run direct commands on Fly.io machines via the Fly SSH console.
npx skills add https://github.com/rubys/showcase --skill fly-ssh
Please help me install this Agent Skill. Skill: fly-ssh Source: https://github.com/rubys/showcase/tree/main/.claude/skills/fly-ssh Command: npx skills add https://github.com/rubys/showcase --skill fly-ssh
This Skill eliminates the frustration of debugging Fly.io deployments by providing clear, actionable guidance on using fly ssh console. It addresses common pitfalls like the lack of a shell, differences between Debian Linux and macOS commands, and ensuring machines are running, allowing you to quickly inspect and troubleshoot production issues.
ps, df, cat, netstat) tailored for Fly.io's Debian environment.Use the fly-ssh skill to check the memory usage of the 'smooth-nav' application on Fly.io and list the top 20 processes by memory consumption.
High-intent search queries and answers about installing and using this skill.
Use fly ssh console to run direct commands on your Fly.io machine and inspect memory consumption. Execute `ps aux` to list processes with memory stats, or use `free -h` to check overall memory usage, then identify and troubleshoot the top memory-consuming processes without needing shell operators.
Yes, fly ssh console executes direct commands without a shell environment. Use the -C option to invoke single commands like `ps`, `df`, or `cat` directly; avoid pipes and redirection since shell operators aren't available in this execution mode.
Before using fly ssh console, verify your machine is running by checking its status in the Fly.io dashboard or via the fly CLI. If no machines are available, start the machine first; connection refused errors often stem from stopped instances rather than SSH configuration issues.
Fly.io machines run Debian Linux, so standard Linux commands like `ps`, `df`, `cat`, `netstat`, and `ls` work directly. However, macOS and Debian command syntax differ—use Debian equivalents, and avoid shell pipes or redirects since direct-command execution doesn't support them.
Use fly ssh console with direct commands to examine logs via `cat /path/to/logfile` and check active ports with `netstat -tuln` or `ss -tuln`. Run region-specific or multi-application workflows by targeting the correct machine and application before executing inspection commands.
Common errors include "no machines available" (start the machine first) and "connection refused" (verify machine is running and in the correct region). Understanding Fly.io's no-shell execution model and using explicit machine-start checks before SSH reduces troubleshooting friction significantly.
dennisonbertramAutomate multi-region Fly.io deployments and infrastructure orchestration using the fly CLI.
albumentations-teamAnalyze benchmark result JSON to detect slow transforms, warmup instability, and regressions.
andy-austinDeploy and manage Fly.io applications for Quipu Brain and Hands services.
bishwashereInspect remote Linux/Unix hosts over SSH for disk, processes, and health.