When you connect your application to GitHub, Encore will begin to automatically provision ephemeral Preview Environments for each Pull Request. Preview Environments are fully functional, isolated, environments where you can test your application as it would run in production.
Preview Environments are named after the pull request, for example PR #72 creates a Preview Environment named
pr:72 with the API base url
You can also view the environment in the Cloud Dashboard, where the url will be
Preview Environments run in Encore's free development cloud, removing the need to manually manage and pay for your own sandbox environments. This gives you a cost-efficient way to validate your changes before they are merged and deployed to the primary environment.
See the infra docs if you're curious about exactly how Preview Environments are provisioned.
Preview Environments make it really easy to collaborate and test changes with your frontend. Just update your frontend API client to point to the
This is a one-line change since your API client always specifies the environment name, e.g.
If your pull request makes changes to the API, you can generate a new API client
for the new backend API using
encore gen client --env=pr:72 --lang=typescript my-app