Terrateam has a very expressive configuration file. We need it because, as any Terraform or Tofu user knows, there is no standard on how you should design your repository. The Eternal September question of r/terraform is asking how to structure a repository for multiple environments. It comes up so much that we even wrote a blog post about it. Terraform and Tofu users, in my experience, are especially concerned with how to structure a repository. I think this is because Tofu is so low-level. ...| Blog on pid1
My favorite Google product for a long time has been the Chromecast. It solved a problem, it was easy to use, and it just worked. It also turned watching YouTube into kind of a social experience, where everyone could connect and add videos to the queue. My favorite thing about it is you just had to be on the network to cast. I didn’t have to make an account and add myself to a friend’s house group or something. You just connect to whatever Chromecast-capable device is on the network and st...| Blog on pid1
Note I will refer to OpenTofu in this post, however everything I say applies equally to Terraform. Tofu uses HCL to define infrastructure. It’s fairly simple. Closer to a configuration language than a programming language. Choosing a DSL for a product can be hit-or-miss, but in this case I’m fairly pro-DSL. Given the goals of Terraform (the project OpenTofu is a forked from), using something like YAML would quickly become difficult to manage infrastructure at scale, and a full-fledged pro...| Blog on pid1
Note I will refer to OpenTofu but unless otherwise specified, everything applies to Terrraform as well. OpenTofu recently released 1.9.0 with provider for_each support, also known as dynamic provider configuration. This is actually a pretty old request. The original ticket is from 2019, before even version 1.0.0 of Terraform was released. A provider is a library that enables Tofu to interact with services. They cover everything from the major cloud providers to services like PagerDuty. To use...| Blog on pid1
At Terrateam, we are big fans of Fly.io. The service is hosted there and it’s served us well. Just deploy your TOML file, get your infrastructure, do something else with the rest of your day. One of the interesting sides of Fly is that they invest heavily in server-side SQLite. They’ve written a number of blog posts on how they enable server-side SQLite: I’m All-In on Server-Side SQLite - Ben Johnson, the author of BoltDB, joins Fly to work on Litestream, a SQLite replication solution. ...| pid1