deploying-app
deploy the Wasp app to Railway or Fly.io using Wasp CLI.
When & Why to Use This Skill
This Claude skill streamlines the deployment of Wasp applications to cloud platforms like Railway and Fly.io. It automates the end-to-end release process, including pre-deployment validation, provider-specific configuration, and OAuth redirect setup, ensuring a reliable and efficient transition from development to production environments.
Use Cases
- Automating the deployment of full-stack Wasp applications to Railway or Fly.io via the Wasp CLI.
- Performing pre-deployment checks to validate configurations and prevent deployment failures.
- Configuring production-ready OAuth redirect URLs for social authentication providers like Google or GitHub.
- Managing and recovering from interrupted deployment processes by identifying safe-to-rerun commands.
| name | deploying-app |
|---|---|
| description | deploy the Wasp app to Railway or Fly.io using Wasp CLI. |
deploying-app
Pre-Deployment
- Run a pre-deployment check via validating-pre-deployment to validate configuration.
- present the list of supported
wasp deployproviders under the "Wasp Deploy" section of the docs and ask the user to choose one. - follow the steps from the chosen provider's guide to deploy the app.
OAuth Redirect URLs
If they user is using OAuth providers, inform them that they need to add the redirect URLs to the OAuth providers in the provider's dashboard. For example: https://your-server-url.com/auth/google/callback
More info can be found in the Wasp Social Auth Providers docs.
Deployment Interrupted
Safe to rerun: wasp deploy <provider> deploy
DO NOT rerun: wasp deploy <provider> launch commands (one-time only)