Monitoror is a single file app written in Go. It can run on Linux, macOS, or Windows. You can view a live demo here.
This tool is surrounded by mountains of marketing speak, but it does seem like it offers a quick way to spin up different dev environments, which is cool. It has built-in recipes for WordPress, Drupal, LAMP, MEAN, and more. Here’s how you get started on Drupal 7, for example:
lando init \ --source remote \ --remote-url https://ftp.drupal.org/files/projects/drupal-7.59.tar.gz \ --remote-options="--strip-components 1" \ --recipe drupal7 --webroot . \ --name hello-drupal7
You can use these out of the box or start with a base language and mix in the things you need from there. Kinda like Docker Compose? Yeah, kinda like Docker Compose:
You can think of Lando as both an abstraction layer and superset of Docker Compose as well as a Docker Compose utility.
Arijit Mukherji on The New Stack:
We all have our favorite urban legends. From cow tipping to chupacabras, these myths persist despite a lack of definitive proof (and often evidence to the contrary). Technology isn’t immune to this phenomenon. It has its own set of urban legends and myths that emerge alongside new technologies and continue well into mass adoption. As organizations consider the shift from monitoring to Observability, I hear three common misperceptions. It’s time to debunk the myths.
Includes interview questions, notes, and useful links to other resources to continue your learning.
If you are a system administrator, or just a regular Linux user, there is a very high chance that you worked with Syslog, at least one time. On your Linux system, pretty much everything related to system logging is linked to the Syslog protocol. Designed in the early 80’s by Eric Allman (from Berkeley University), the syslog protocol is a specification that defines a standard for message logging on any system.
This is pitched as “everything that you need to know about Syslog.” From what I can tell, it might just live up to that pitch. It’s high quality and thorough.
Almost any slog can be turned into a do-nothing script. A do-nothing script is a script that encodes the instructions of a slog, encapsulating each step in a function. For the example procedure above, we could write the following do-nothing script:
Containerization technologies are one of the trendiest topics in the cloud economy and the IT ecosystem. The container ecosystem can be confusing at times, this post may help you understand some confusing concepts about Docker and containers. We are also going to see how the containerization ecosystem evolved and the state of containerization in 2019.
Put on your swimming suit, because this is a deep dive. 🏊♀️🏊
Two new terms have recently emerged around software delivery: Software Defined Delivery and Progressive Delivery. Why? How do they relate to Continuous Delivery?
Several forces today make delivery increasingly complex. Notably, proliferation of repositories, with hundreds of small projects replacing a handful of monoliths; desire for greater automation to realize the full potential of CD across multiple environments; the rise of feature flagging; and increased evidence (such as the Equifax debacle) of the need to bake security into the delivery process.
There’s another gorilla to consider for container orchestration.
Kubernetes is the 800-pound gorilla of container orchestration. It powers some of the biggest deployments worldwide, but it comes with a price tag.
Especially for smaller teams, it can be time-consuming to maintain and has a steep learning curve. For what our team of four wanted to achieve at trivago, it added too much overhead. So we looked into alternatives — and fell in love with Nomad.
From the Nomad website:
HashiCorp Nomad is a single binary that schedules applications and services on Linux, Windows, and Mac. It is an open source scheduler that uses a declarative job file for scheduling virtualized, containerized, and standalone applications.
Anyone from the community with experience using Nomad? Let us know in the discussion below.
The new changelog.com setup for 2019 is packed with exciting features that are too good to keep to ourselves. Since the infrastructure code is already public and has been running changelog.com for a few months now, the value that we are sharing is proven to us.
Consider adding these mechanisms to your services and making them clearly visible and usable in the README. The poor soul having to solve problems late at night will thank you.
Who knew an audio post-mortem could be so fun to listen to!
On Thursday, November 8, Basecamp 3 went down for almost five hours. It was the worst outage to hit the company in a decade and a stress test of Basecamp’s practices around internal communication, customer support, and calm work. Today’s episode goes inside the company on November 8 to see how the outage unfolded.
Crossplane provides a universal cloud computing API. Control your workloads across clouds and on-prem environments from one unified place.
Nobody wants to be locked in to their current cloud provider. With Crossplane (and a new breed of ‘multi-cloud’ tools like it), you can spread your application across multiple cloud providers at a single time, migrate managed services across multiple clouds, and more.
We might be looking at the future of cloud computing, right here. I’m sure this will be a hot subject at this week’s KubeCon in Seattle.
(Adam is onsite covering the event. Find him and say hi if you’re attending.)
DevOps and Site Reliability Engineer(SRE), both seem to rule the world of software development, and at the same time, both appear to overlap or confuse people to some extent. Today, we will try to analyze both the terms and see if we can see some differentiating factors between the two.
“Naming things is hard” applies to so much more than merely code.
Tanya Janca’s new live video show about “Sloppy DevOps” sounds like a lot of fun:
A free online show dedicated to the art of implementing DevSecOps, includes free workshops, lessons and nerd-er-ific discussions!
Sid Sijbrandij and the team at GitLab compared GitLab CI with the three Jenkins variants. Here’s what they learned…
The many plugin combinations for Jenkins has made Legacy Jenkins hard to configure and brittle when updating. Cloudbees is introducing two new versions of Jenkins to remedy the problem: Cloud Native Jenkins will start from scratch, while Jenkins Evergreen will focus on a set of essential plugins. GitLab CI adds new functionality in the main code base, avoiding the need for needless configuration and ensuring everything still works when updating.
Also to note — according to a recent Forrester report GitLab CI and Jenkins/Cloudbees are two of the four leading products for CI.
In this new series, we’ll focus on DevOps monitoring and observability tools. Over the next few weeks, we’ll explore metrics aggregation and monitoring, log aggregation, alerting and visualizations, and distributed tracing. Alternatively, you can download the entire open source guide to DevOps monitoring tools now.
Today, we are open-sourcing the code behind Changelog’s infrastructure as is, and are giving you the opportunity to influence the way we continue investing our time.
I’ve wanted this for years, but apparently never enough to build it myself:
A passive monitoring tool written in Python & Django. Set up your cron jobs, backup scripts, weekly email sending scripts, nightly data import jobs etc. to ping this service when they complete. When they don’t send a ping on time, you receive an alert.
The service offers a generous 20 free checks before you start paying. And since it’s an open source Django app, you can set it up to run on your own infrastructure too.
This checklist covers monitoring, infrastructure, culture, code, and protection. It even helps you focus based on the stage of your company (assuming you are venture backed).
Travis CI announced the merging of their worlds to combine their .org (open source) and .com (paid) efforts under one roof. Smart move!
Over time we found two platforms lead to confusion for people using travis-ci.org extensively, or together with travis-ci.com … when we decided to move our GitHub integration to GitHub Apps at the beginning of this year, we realized it was a great opportunity to dive into merging travis-ci.org and travis-ci.com into a single platform.