Infrastructure as code: define your services in a file
What it means to declare your services in a file kept in your own repository, what that buys a team over time, and how Voroa services are created today.
What this covers
Infrastructure as code means your services, their sizes, their variables and the databases they use are described in a file in your repository rather than clicked together in a dashboard. Three things follow from that. The setup is reviewable, because a change to it goes through a pull request like any other change. It is repeatable, so a second environment is created by applying the same file rather than by remembering. And it stops being knowledge that lives in one person’s head.
Defining your services in a file is not available on Voroa today. Services are created and configured through the dashboard.