Today, we are glad to release the Koyeb Terraform Provider and announce that we are a Hashicorp Technology partner. Terraform has become an essential tool for many developers who manage infrastructure and applications running in the cloud. We are excited to offer our users a way to manage their Koyeb resources using Terraform.

Imagine waking up one day and realizing that the world is nothing more than a computed simulation, and everything is connected to one configuration file. Let’s say you have the exact configuration file of that simulation in your hand. Out of curiosity, you add some text to the configuration file, and BOOM, your appearance change; you grow a bit taller, achieving that dream built of yours. Sounds magical, right? This is what DevOps Configuration Management is about.

“Good software, like wine, takes time” – Avram Joel Spolsky But do we have that much time? The statement was perfect when SDLC still relied on the waterfall and agile methodologies. But the scenario has drastically changed since then. DevOps is ruling the SDLC world today, and tools supporting the process are everyone’s favorite. And CI/CD is the modern software development practice every DevOps engineer swears by.

Kubernetes is a powerful platform that comes with many features to help engineers run their applications more efficiently. However, as you gain more experience and deploy more workloads, you’ll inevitably start looking for ways to optimize Kubernetes performance. There are many ways to approach optimization. On one hand, you could work exclusively with the tools and configurations provided by Kubernetes itself; on the other, you could reap the benefits of third-party tools.

DevOps vs CI/CD has been one of the key debates in the recent few years. This is due to the fact that these two software development methodologies have gained popularity in recent years. The goal of DevOps is to improve the speed and quality of software development and deployment. It does so by breaking down silos between different teams and streamlining workflows. On the other hand, CI/CD is a set of practices and tools that enable continuous integration, testing, and deployment of code changes.

CLI stands for command-line interface, a text-based interface you can use to input commands and perform various operations. If you’ve ever used the dart or flutter commands in your console, you’ve used a CLI. Sometimes, though, you may end up writing a CLI of your own.

As a senior Flutter developer, a big part of my daily job consists of reviewing code, mentoring other developers, and helping them with their problems. One mistake that I noticed developers repeating on many occasions is misusing BuildContext. I analyzed why this happens and came to the conclusion that it is because of an incomplete understanding of what BuildContext is, how it works, and its scope and lifecycle.

Testing Kubernetes Ingress resources can be tricky, and can lead to frustration when bugs pop up in production that weren’t caught during testing. This can happen for a variety of reasons, but with Ingress specifically, it often has to do with a misalignment between the data used in testing and the traffic generated in production. Tools like Postman can be a great way of generating traffic, but they have the drawback of being manually created.

GitHub Actions is a powerful continuous integration and continuous delivery (CI/CD) platform that allows developers to automate build, test, and deployment pipelines. Workflows automatically build and test code whenever an event occurs, such as a pull request or a deployment of merged pull requests to production. Best of all, you can use it without leaving the comfort of your own repository!