With all the different cloud service offerings, hosting solutions, and automation tools, figuring out how to get your app up and running in the cloud can be quite a challenge. In this article, I'll show you how to host your React front-end, Node.js back-end, and database on Google Cloud Platform (GCP) using a single command from an open source tool called Adapt.
After what feels like more work than it should have been (isn't that always the way), we are excited to announce the release of Adapt.js 0.1.0. There have been a whole raft of bug fixes and usability improvements in this release, but the 3 major new features are improved Kubernetes support, including Google Kubernetes Engine (GKE), support for making a local Docker deployment for testing and development, and support for remote Docker registries. We've also automated the release process which will make it easier to deliver regular releases for those of you that like to stay on the bleeding edge of development.
Photo by Lukas Blazek on Unsplash
Having flaky tests in in your CI is a nightmare. You can't tell whether your new code broke something or if it's just those tests being flaky again. So anytime we see strange, random failures in CI for our open source project, Adapt, we try to track down the culprit ASAP. This is the story of how we discovered we were (accidentally) flooding our DNS server with traffic and how we used a DNS cache in Docker to solve the problem.
What is "Infrastructure as Code"? If someone checks a bunch of YAML files into a Git repository, do they suddenly become code? That seems more like "Infrastructure as Files" to me. I suppose that's better than infrastructure as a gaggle of shell scripts and some commands run by hand in the middle of the night in a coffee-fueled haze, but it is a far cry from code. How about a system to define infrastructure that really is like code?
