ReferenceBlueprint spec
Top-level keys
A blueprint has four top-level keys. Ferry ignores each other key with a warning.
envVarGroups: # env groups
- name: shared-settings
databases: # Postgres databases
- name: app-db
services: # services and Redis datastores
- type: web
name: helloA top-level key starts one part of the file.
The four keys
| Top-level key | Contains |
|---|---|
envVarGroups | Env groups: sets of variables that services link to. |
databases | Postgres databases. |
services | Services of each type, and Redis datastores (type: redis or keyvalue). |
projects | The projects of Render. Ferry applies their environments[].services, databases and envVarGroups to this server, with a warning. Ferry has no projects and no environments. |
Other keys
Ferry ignores each other top-level key with a warning. This includes the x- keys that hold a YAML anchor. The anchor continues to work:
x-defaults: &defaults
autoDeploy: false
services:
- <<: *defaults
type: worker
name: queue
repo: https://github.com/acme/queueSee also How Ferry reads values.