Operations | Monitoring | ITSM | DevOps | Cloud

Modules and mixins are, without doubt, great resources that make Ruby so attractive. They give the application the ability to share the code that can be used with ease in other places. It also helps us organize our code by grouping functionalities and concerns, which improves the readability and maintainability of our code. In this article, we will go through the concepts behind modules and mixins.

We’ve been doing some Ruby on Rails development lately, in preparation for PagerTree 4, and we wanted to put together a Ruby on Rails Cheat sheet. This is a quick reference guide to common ruby on rails commands and usage.

Monitoring your application can be a difficult task if you’re just getting started with it. You need to know which metrics matter most and understand which ones you can combine into meaningful graphs. In the (not just holiday ⛄️) spirit of making things smoother for our users, we’ve added a magic dashboard to the Ruby integration that shows you the volume of emails you are sending with ActionMailer.

As we’re doing our best to make monitoring easy, we’ve wanted to make more content that would really show and not just tell you how easy it is to set up monitoring with AppSignal. We’ve been collaborating with Leigh Hallday on making this video for you that will show you everything you need to know about the setup process. We’ll be posting more videos like this on our YouTube channel, so you should subscribe to it if you’d like to get notifications about future videos.

According to a definition of multitenancy, when an app serves multiple tenants, it means that there are a few groups of users who share common access to the software instance. An excellent example of an app that supports multitenancy is the Jira platform, where each company has its subdomain to access the software, for example, mycompany.atlassian.net.

The last 3,650 days of my professional life have been focused on making Rails apps faster. Below are five lessons I've learned the hard way.

If you’ve ever used Ruby on Rails, you’ve probably come across the concept of concerns. Whenever you jumpstart a new Rails project, you get a directory app/controllers/concerns and app/models/concerns. But what are concerns? And why do people from the Rails community sometimes talk badly about them?

Thanks to awesome contributions from the community and the hard work of our integrations team, the Honeycomb Rails integration comes with lots of great features out of the box. This post is an end-to-end tutorial to show you exactly the steps involved, from creating a new Honeycomb team to getting your data in and observing your app in production.