innozverse-flyio-deploy

Automate innozverse API deployments to Fly.io with Fly CLI workflows.

Updated Dec 21, 2025
One-click install
npx skills add https://github.com/lastcow/innozverse --skill innozverse-flyio-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: innozverse-flyio-deploy
Source: https://github.com/lastcow/innozverse/tree/main/.claude/skills/flyio-deploy
Command: npx skills add https://github.com/lastcow/innozverse --skill innozverse-flyio-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quick reference for deploying the innozverse API to Fly.io, managing deployments, checking status, viewing logs, and troubleshooting.

Core Features & Use Cases

  • First deployment: Use fly launch and set secrets before deploy.
  • Subsequent deployments: Use fly deploy for updates.
  • Common commands: Status, logs, SSH, secrets, scaling, and opening the app.

Quick Start

Follow the first deployment steps to launch the app on Fly.io, set secrets, and deploy.

Frequently Asked Questions about innozverse-flyio-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy an API to Fly.io using the CLI?

Deploy to Fly.io by running `fly launch` for initial setup, configuring your fly.toml with port 8080 and health endpoint settings, then executing `fly deploy` to push your application. Set required secrets with `fly secrets set` before deploying to production environments.

What's the difference between initial and subsequent Fly.io deployments?

Initial deployment uses `fly launch` to create and configure your app on Fly.io, including setting secrets and health checks. Subsequent deployments use `fly deploy` for updates, which applies code changes without reconfiguring the app infrastructure or resetting secrets.

How do I troubleshoot a Fly.io deployment?

Troubleshoot deployments by checking app status with `fly status`, viewing logs with `fly logs`, and accessing the running machine via `fly ssh`. Verify health checks are passing and review secret configuration to isolate runtime issues in development and production.

Can I manage secrets and scaling for Fly.io apps from the CLI?

Yes, manage secrets with `fly secrets set` and `fly secrets list` to store environment variables securely. Scale machines with `fly scale` and monitor app availability using `fly open` to launch the deployed application directly from the command line.

What configuration does Fly.io need for health checks and auto-stopping?

Configure fly.toml with a health endpoint, set `auto_stop_machines` to manage idle instances, and specify port 8080 for your application. Fly.io uses these settings to verify app health and automatically suspend machines when not in use, reducing operational costs.