setup-deploy

Multi-platform deployment configuration is automated by detecting the target platform, production URL, health check endpoints, and deploy status commands. The detected settings are then persisted to CLAUDE.md to enable repeatable, automatic deploys across different hosting environments.

Yes, the deployment setup works with Fly.io, Vercel, Heroku, Render, Netlify, GitHub Actions, and custom environments. It detects the specific platform in use and configures the deployment pipeline settings accordingly to ensure proper integration.

CLAUDE.md is used to store centralized deployment configuration for CI/CD pipelines. By persisting platform detection, production URLs, health checks, and deploy commands to this file, future deployments become automatic and repeatable without requiring manual setup steps.

To reconfigure an existing deployment pipeline, run the setup-deploy workflow against your project repository. It will detect the new target platform, update the production URL and health check endpoints, and overwrite the deployment configuration stored in CLAUDE.md.

Yes, you need access to the project repository to set up cross-platform deployment. The configuration process reads or creates the CLAUDE.md file directly within the repository to store the detected platform settings and deployment commands.

Manual deployment configurations are inconsistent because detecting platform specifics, production URLs, and health checks across providers requires repetitive manual steps. Automating this detection and saving the results to CLAUDE.md standardizes the setup for future automatic deploys.