An introductory tutorial on making event scheduling management more accessible and configurable to administrators through database driven admin interfaces in Rails.
Category: Ruby On Rails
Tip: Annotate ActiveAdmin resources along with models
Annotate is a very useful utility for annotating schema information in Rails models. The gem prepends (or appends, as per your configuration) a summarized information about the table schema in each model file as comments) – saving multiple roundtrips to the schema.rb file during coding.
Useful delegation patterns for Rails
An exploration into the delegation pattern and how it can be useful in various aspects of a Rails application
Boost your content focussed site with Structured Page Fragments
Eliminate full page refreshes and reduce page transition latency, in your your Rails sites, using SPF.js – a library for dynamic page updates from Youtube.
Gathering and Visualizing metrics from Rails application using InfluxDB
Checkout how using a distributed time series database like InfluxDB can help keep track of application events from all multiple Rails processes in a centralized hub.
Dealing with JSON data in Active Admin
While the default form fields of Active Admin are decent for most use cases, there are special cases like JSON data stored in relational databases, for which the built in controls might prove to be inadequate. This post explains how to handle the same.
Leveraging the strategy pattern in Rails – I
Strategy pattern is a well known software design pattern. In this post we explore how to apply it in the context of a Rails application.
Allowing multiple emails for a user in Devise
Devise is an incredibly popular authorization gem for Rails. Unfortunately allowing a user to log in through multiple emails is not as straightforward as one might expect. This post outlines a way to do just that.
Optimizing space taken by type column in Rails STI
The Single Table Inheritance facility in Rails is quite awesome in that it is simple, minimal and easy to understand. However that simplicity comes with a small price – the type column stores the full name of the relevant class as a string. This becomes especially unweildy if you scope your models inside a module.