deployment-manager

Automate NutriProfile deployment to Fly.io and Cloudflare Pages.

Updated Dec 22, 2025
One-click install
npx skills add https://github.com/ayia/NutriProfile --skill deployment-manager-ayia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-manager
Source: https://github.com/ayia/NutriProfile/tree/main/.claude/skills/deployment-manager
Command: npx skills add https://github.com/ayia/NutriProfile --skill deployment-manager-ayia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NutriProfile deployment is complex and error-prone; this skill provides a structured approach to reliably push backend and frontend to production, manage secrets, and perform health checks.

Core Features & Use Cases

  • Backend deployment to Fly.io (nutriprofile-api)
  • Frontend deployment to Cloudflare Pages (nutriprofile.pages)
  • Secrets management, health checks, and migrations
  • Rollback and troubleshooting workflows

Quick Start

Navigate to the backend directory and run flyctl deploy to publish the API and verify health afterwards.

Frequently Asked Questions about deployment-manager

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

FAQPage Schema
How do I deploy a full-stack application backend to Fly.io and frontend to Cloudflare Pages?

To deploy a full-stack application, you push the backend to Fly.io using flyctl deploy and publish the frontend to Cloudflare Pages. This structured deployment process applies migrations and verifies health endpoints to ensure both services run reliably in production.

What is the best way to manage environment secrets during production deployment?

Environment secret management during production deployment involves securely configuring sensitive variables for both backend and frontend services. This deployment workflow explicitly handles environment secrets to ensure applications authenticate correctly without exposing credentials in the codebase.

How do I perform a safe rollback when a production deployment fails on Fly.io?

A safe rollback reverts the production deployment to a previous stable state when health checks fail or errors occur. This troubleshooting workflow ensures you can safely roll back the Fly.io backend and Cloudflare Pages frontend without losing data integrity.

Does this deployment process handle database migrations and health checks automatically?

Yes, the deployment process handles database migrations and health checks as explicit deployment steps. After applying migrations to the Fly.io backend, it verifies health endpoints to confirm the application is fully operational before completing the rollout.

When do I need to run health checks after deploying to Cloudflare Pages and Fly.io?

You need to run health checks immediately after deploying to Fly.io and Cloudflare Pages to validate that the production environment is stable. Verifying health endpoints confirms the backend API and frontend services are successfully serving traffic without startup errors.