Re:Show HN: Digger.dev – A PaaS that generates Terraform, in...
by igorzij on Wednesday July 21, 2021 @01:03PM
(#27908924)
We have a concept of Targets - essentially "template generators" that follow a particular architecture and include modules for most commonly used services.
When you connect your repositories Digger asks you to confirm a few basic options like your container port or build command for your webapp. By connecting a repository you define a Service. You can also define Resources like databases. This way you describe the "logical structure of your stack". No infrastructure is created at this point yet.
Then you create environments - and it is at this point Terraform is generated, combining the "logical structure" of the stack with this particular environment's configuration.
When you connect your repositories Digger asks you to confirm a few basic options like your container port or build command for your webapp. By connecting a repository you define a Service. You can also define Resources like databases. This way you describe the "logical structure of your stack". No infrastructure is created at this point yet.
Then you create environments - and it is at this point Terraform is generated, combining the "logical structure" of the stack with this particular environment's configuration.
More here: https://learn.digger.dev/overview/how-it-works.html