Apply the blueprint

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

Env groups. Ferry creates the env groups first.

1 / 4

Terminal

ferry blueprint apply render.yaml

The trigger of each first deploy is blueprint.

Terminal

ferry deploys NAME
ferry logs --deploy ID -f

The datastores start in the background.

Terminal

ferry db ls

Terminal

ferry show NAME
ferry db show NAME

The two commands print the Memory limit and the CPU limit. Thus you see what the plan gave to the service or the datastore.

If a first deploy fails

A first deploy can fail because its database was not ready. Deploy the service again.

Terminal

ferry deploy NAME

Preview the changes

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

Set the values that Render did not sync

Ferry does not create a variable with sync false. Set its value with the CLI.