The voroa.yaml blueprint reference
What a blueprint file declares, from each service and its size to variables and databases, and how services on Voroa are configured through the dashboard.
What this covers
A blueprint file is the declaration of everything a platform should create for your application: each service and its type, the size it runs at, the branch it deploys from, the variables it needs, and the databases it depends on. It is kept in your repository next to the code, so the two move together and a change to your infrastructure has an author, a date and a review like any other change. The value shows up most when you have to recreate an environment, because the file is the whole answer.
Voroa does not read a blueprint file today, and there is no voroa.yaml format to reference. Services are configured through the dashboard.