FerryDocs
GuidesMigrate from Render

Preview the changes

A dry run shows what Ferry creates and which keys it ignores. It changes nothing.

Edit on GitHub
Terminal
$

Run the in the directory of render.yaml. With no file argument, ferry blueprint apply reads ./ferry.yaml, then ./render.yaml.

Read each warning

Output
Warnings:
  ! blueprint: ignoring unsupported key 'previews'
  ! database 'shop-db': ignoring unsupported key 'region'
  ! database 'shop-db': ignoring unsupported key 'ipAllowList'
  ! service 'shop-web': autoDeployTrigger 'checksPass' is not supported; deploying on every commit
  ! service 'shop-web': ignoring unsupported key 'region'
  ! service 'shop-web': ignoring unsupported key 'preDeployCommand'
  ! service 'shop-web': ignoring unsupported key 'scaling'
  ! key value 'shop-cache': ignoring unsupported key 'ipAllowList'
  ! key value 'shop-cache': ignoring unsupported key 'maxmemoryPolicy'
  ! service 'shop-worker': registry credentials are not supported; the image must be pullable anonymously
  ! service 'shop-web': env var 'STRIPE_KEY' is marked sync: false; set it with `ferry env set shop-web STRIPE_KEY=...`

Run without --dry-run to apply.

Each warning is a feature of Render that your app does not get on Ferry. The pages from Top-level keys to Plans explain them.

Before you migrate

You need a Ferry server, the ferry CLI, and repositories that the server can clone.

Apply the blueprint

Ferry creates the env groups, then the datastores, then the services, and deploys the new services.

On this page

Read each warning