Reference
Blueprint spec
A blueprint is one YAML file that describes your env groups, datastores and services.
You write your env groups, datastores and services in one file.
1 / 5
A blueprint describes your env groups, your Postgres databases, your Redis datastores and your services in one YAML file.
An apply creates what is not there and updates what changed. It never deletes. A second apply of the same file changes nothing.
Ferry reads the render.yaml format of Render, with its camelCase keys. It supports a practical part of this format. Ferry ignores a key that it does not support, with a warning and never an error. Thus a render.yaml that you have applies as it is. The plan of Render becomes the resource limits of the containers.
Apply a blueprint
ferry blueprint apply --dry-run # show what would change
ferry blueprint apply # apply ./ferry.yaml, else ./render.yaml