In this blog post, we provide the necessary steps to setup a single-node standalone Consul server to be used as TF state backend.
In doing so, we aim to provide idempotent and reproducible codes using Tofu and Ansible, for the sake of disaster recovery as well as enabling team collaboration within version control system.
In this blog post you will learn how to authenticate and deploy your frontend code to Azure CDN, backed by Azure Blob Storage to deliver low-latency static website to your users.
The objective is to avoid hard-coded credentials and only employ OpenID Connect to establish trust relationship between the Identity Provider (GitHub) and the Service Provider (Azure).
Preview environment is where you see a live state of your changes from your pull request before being merged into the default branch. It gives you a look'n feel of what it would be like if you merged your changes.
Kubernetes on the other hand, is what powers the production setups. But that's not all it can do for you. I have spun up preview environments in Kubernetes with different technologies in the past.
And in this blog post, I will show you how to achive this using FluxCD Operator.
In the recent few years, I keep seeing people being more aware of their privacy and taking it into their own hands.
More and more solutions are emerging through the community that address the critical part of our society and personal life; privacy!
In this blog post, I will introduce you to Ente, the Google Photos alternative.
You will see the codes required to deploy the server into a Kubernetes setup and host the frontend using GitHub Pages.
Stick around till the end if that's your cup of tea.
Building and deploying static sites is rarely an issue these days. Most of the PaaS providers already have full support for your live and your preview environments and a clean integration with your favorite Git provider.
However, some organizations may choose to stick with big players like GCP for various reasons.
In this blog post, you will learn how to build your frontend and deploy your static files to GCP bucket using GitHub Actions and serve it behind GCP CDN.
In this approach we will employ OpenID Connect to authenticate GitHub Actions runner to GCP API to avoid passing hard-coded credentials (Actually, GCP calls this Federated Workload Identity but it is unsurprisingly based on OIDC).
If this sounds interesting to you, let's not keep you waiting any longer.
In this blog post, you will learn how to leverage GitHub Actions to deploy static files to the GitHub Pages of another repository.
This can be useful if you keep your source code in a private repository, but also, you may find additional reasons to need this setup.
Stick around till the end to find out how to do this with OpenTofu.
If you're a software engineer in any tier, there's a good chance that you're already familiar with the language and syntax of JavaScript. It has a very low barrier for entry and that is one of its strongest suits and what makes it so widely adopted and popular.
In this article, you'll learn how to deploy a JavaScript application to AWS Lambda using the principles of GitOps and with the help of OpenTofu as the Infrastructure as Code and GitHub Actions for the CI/CD pipeline.
Stick till the end to find out how.
Monorepo is the practice of storing all your code in a single repository, which can be beneficial for code sharing, dependency management, and version control.
However, there is no free lunch! As your codebase grows, managing builds become unavoidably complex and time-consuming. This build time is billed on your organization and it can get quite costly.
In this blog post, we'll explore the challenges of building only changed applications in a monorepo and discuss strategies to optimize your workflow with selective builds.
If this gets you excited, let's dive in!
Have you ever been frustrated at long merge queues? Did you ever wish there was a better and faster way to get feedback on your code changes and approval from your team members?
You may have also been on the other side of the table, reviewing pull requests and wishing there was a better way to actually test the revisions before approving it; giving you a sense of what it would feel and look like if it were to merge.
Netlify and other frontend hosting services have spoiled us with the ability to spin up a live instance of the application for each pull request for static files. But what about backend applications? How can we achieve the same and deploy our backend for every new proposed change in pull requests?
In this blog post, we will explore how to set up preview environments for each pull request using GitHub Actions and Kubernetes. This guide includes spinning up the application as a live instance with an internet accessible URL to preview and verify the changes before they find their way into the main trunk.
GitHub Actions is a great CI/CD tool to automate the daily operations of your application lifecycle in many ways. It comes with a lot of features out of the box and even the ones that are missing are wholeheartedly provided by the community.
There are many great and brilliant engineers working daily to provide a fantastic experience for the rest of us.
In this blog post, you will learn how to perform your integration testing using GitHub Actions with all its dependencies and services spun up beforehand.
Stick around till the end to find out how.