Cloud 66 offers a range of deployment options for Rails applications, each offering different benefits and trade-offs.

We have created a simple Rails 7 application to showcase how easy it is to deploy to Hetzner Cloud with Cloud 66.

This is the first part of a multi-part post focusing (mostly) on front end search and Command Palettes. If you are not familiar with Command Palettes, they are a power-user's dream: a universal overlay on your webpage that's triggered with a key shortcut (usually Command + K) and allows your users not only to search the content but also perform actions on your website. The goal here is to "keep the user's hands on the keyboard" (and away from the mouse), when using your application.

In the first of this two-part series, we covered how to set up AppSignal in a Ruby on Rails application for many great insights out of the box. AppSignal can automatically track errors, monitor performance, and report metrics about some dependencies. But, in many cases, each of our applications behaves in different ways, so we'll want more than just generic monitoring. In this post, we will run through adding custom instrumentation and monitoring to a Ruby on Rails application.

This case study showcases La langue française, an online learning platform and publication that teaches people how to speak French. La langue française hosts their Ruby on Rails application on Vultr with the help of Cloud 66.

Monitoring an application’s performance is the basics of building a successful software product. With the popularity that Rails has always been riding on in the start-up world, it makes all the more sense to look for tools that help you keep your Ruby on Rails application in shape. In this guide, we will look at some of the top APM tools for Rails applications and compare them along some standard benchmarks to help you get an insight into which tool fits your use case the best.

There are many ways to add search functionality to a Rails application. While many Rails developers choose to use the native search functionality built into popular databases like MySQL and Postgres, others need more flexible or feature rich search functionality. ElasticSearch is probably the most well known option available but it has its own issues. Firstly, it is a resource hungry beast. To run ElasticSearch properly in production, you need a few beefy servers.

Rails is a classic on Ruby for a reason. The framework is powerful, intuitive and the language has a low entry bar. However, being designed when systems existed on a single server, standard Rails logging is excessively fractionalized. Even on a single server, a straightforward call can quickly turn into seven unique, unconnected logs.

Today I want to show you how to build a polymorphic select box in Ruby on Rails. Seems trivial, but it’s not. Let me show you the way and save you some time.

Logging is useful in building, managing and debugging Rails applications. Most logging functionalities are built into the application, and it is fairly simple to find the logs. However, as your applications scale up in volume, it becomes difficult to trace the source of an issue. That’s when you want to implement a cloud based log management system to get a unified view of all logs from your Rails application.