In the first part of this series, we outlined the basic steps you need to take in order to begin setting up a developer environment, installing your first app, and making use of the first commands. In this installment, we’ll aim to answer the most common questions about what was installed, how it works, and how the various pieces interact with each other. Additionally, this post will lay out all the different components that are involved in the overall lifecycle of a Mattermost app.

Before I introduce myself, I first want to highlight a monumental day in our company’s story. Today, we begin writing a new chapter under a new company name. We’ve decided to name the entire company after our flagship product, the ultra-popular GitKraken Client. Why make this move now? It’s much more than a cosmetic name change. Today ushers in the next phase in our evolution – one in which we will become the premier provider of Git tools for developers around the world.

It wouldn’t be Cybersecurity Awareness month without some spooky-themed blogs with language focused on Fear, Uncertainty, and Doubt (FUD). Luckily, it’s the end of November now, and this isn’t that kind of blog, but what was true in October is still true today. I won’t tell you that you need to be afraid of bad actors infiltrating your security defenses and wreaking havoc in your infrastructure. Why? Because you are likely stressed enough already. Don’t you think?

Perhaps because so few of us have been able to travel recently, or perhaps because wanderlust is just good fun, we’ve been wondering as to where the best place to live is as a DBA. And not just where pays the most, or where the opportunities are, but where would truly be the best place to live day-to-day. Some of the findings might surprise you! If you live in any of the places mentioned, we’d love to hear about your experience of living there in a comment below.

The JFrog Security research team continuously monitors popular open source software (OSS) repositories with our automated tooling, and reports any vulnerabilities or malicious packages discovered to repository maintainers and the wider community. Most recently we disclosed 11 malicious packages in the PyPI repository, a discovery that shows attacks are getting more sophisticated in their approach.

Although refactoring isn’t typically listed as one of the core phases of the software development lifecycle, you cannot leave it out if you intend to keep code running efficiently. The unfortunate thing about software is, it doesn’t usually age very well. Even seemingly perfect source code progressively decays over time — due to the ever-morphing tech ecosystem.

Shipa in your organization/team can help usher in the next generation of engineering efficiency and developer experience. Though like any platform, there requires some wiring to bind Shipa to infrastructure. In this modern example, can plug into your IaC strategy in creating Kubernetes clusters then auto-wires all of the needed Shipa pieces at cluster creation time.

In the world of a site reliability engineer (SRE), failure is not only an option, but also expected. Systems, web applications, servers, devices, etc., are all prone to performance issues and unexpected outages at some point. It is an unavoidable fact. These unexpected failures can lead to huge revenue losses, customer trust and depending on the industry, maybe fines. Fortunately, SRE incident management is one of the core practices used to limit the disruption caused by unexpected issues.

When you’re working with a Continuous Delivery workflow, you rely on building and deploying your websites in such a way that any improvements can be released into production any time. Identifying and fixing failures quickly is key to enabling rapid development cycles. But what happens when you’re looking into a failed build step, with no clue as to how to address it? You can now share links to specific lines within the activity logs.

One of our customers recently got their first bill after moving their Linux and Windows workloads to Azure. Their bill was astronomical! They struggled to answer the question, “how much will it cost?” and their initial cost assessments were vague at best. Here’s what they did.