Menü
deploy the Wasp app to Railway or Fly.io using Wasp CLI.
| name | deploying-app |
| description | deploy the Wasp app to Railway or Fly.io using Wasp CLI. |
wasp deploy providers under the "Wasp Deploy" section of the docs and ask the user to choose one.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.
Safe to rerun: wasp deploy <provider> deploy
DO NOT rerun: wasp deploy <provider> launch commands (one-time only)
Add Wasp's built-in features to your app — auth, email, jobs, and more. These are full-stack, batteries-included features that Wasp handles for you. Use when the user wants to add meta tags, authentication (email, social auth providers), email sending, database setup, styling (tailwind, shadcn), or other Wasp-powered functionality.
configure Wasp framework features and set up their app's branding (meta tags, SEO), authentication (email, social auth providers), database, email providers, styling (tailwind, shadcn), etc. Use when the user wants to add or set up Wasp-specific functionality.
Shows the Wasp plugin's available features, commands, and skills.
Start the Wasp dev server and set up full debugging visibility. This includes running the server (with access to logs), and connecting browser console access so Claude can see client-side errors. Essential for any development or debugging work.