Prerequisites
- A Git repository containing your application and its production build command.
- A Ravion account with your AWS account connected. Start free at Ravion signup.
- The Ravion CLI installed and authenticated. See CLI installation.
my-org/my-app as a placeholder. Replace it with your repository before applying the config.
Set up this RedwoodJS app for Ravion ECS hosting.
Configure the deployment
Ravion provisions the VPC, cluster, web service, and database in your AWS account. This example uses Railpack for the build. Usebuild_source: dockerfile instead when you need a custom Dockerfile.
Build the Redwood API and web sides with yarn rw build. Redwood’s production server command depends on the generated deployment target; use the start command from your Redwood version’s deployment documentation.
ravion.yaml
DATABASE_URL and Redwood’s required runtime settings through Secrets Manager. The module schema does not automatically wire RDS outputs into ECS secrets; create the secret from the database outputs before applying the service.
Apply and connect your domain
Next steps
Custom domains
Point a domain at your deployed service and manage its certificate.
Project config
Preview and apply Ravion configuration from source control.
Pipelines
Add approvals, migrations, and deployment automation.
Logs and metrics
Inspect deploy output and production health in Ravion.