Rails middleware for Lograge with support to log exceptions from Rails and ActiveJobs

Generate a Rails app with application templates

Rails Material Design Icons provides the web fonts and stylesheets as a Rails engine for use with the asset pipeline.

Easily manage your meta tags in rails projects

Wraps a reloadable class to be used as Rails middleware.

Dead simple nested layouts for Rails

Rails ojects logger helper

Rails gem to facilitate simple payments with Ogone.

We renamed to Codeship.io and you can configure your project now through the website at https://www.codeship.io

Allow to developers increase rails performance in some cases

A "Productized Rails Application" is a single generic application having a hierarchical structure wherein add-ons and tweaks for concurrent versions of the application are possible without affecting the core "generic" code base. You might use this, for example, if you want to maintain a common shopping cart code base that all of your clients use, while still providing flexibility for paid add-ons or site-specific needs.

command line rbline prof for rails apps

A simple Rails 3 engine gem that adds the issues engine (Redmine) to any Rails 3 application.

Web requests in Rails get assigned a unique request id. To access this id in a threadsafe manner, you can simply call ```RailsRequestId.get```

Graceful session key rotation for the signed cookie store in Rails 3.

A simple way to initialize objects in rails controllers using callbacks and ruby magic!

Simple DSL to validate params (and coerce them to the desired type) that fall outside of Rails' default parameter whitelisting and ActiveModel validations system. The common use cases are searching and sorting, whether from an HTML form or via a JSON API.

Towards a SLA-based Rails application

rails_sorbet_enum is a gem that makes it simple to use typed Sorbet T::Enums as fields on ActiveRecord models.

Remember the route prior to the current controller and redirect/use later In rails project, one common case is one form used to create or update an object can be routed from more than one page, when the object is created or updated, it should be redirected back to wherever it came from. Rails redirect_back doesn't work in this case because: 1. redirect_back in create/update action will go back to new/edit form. 2. usually the form is re-rendered if any error exists, which basically breaks the redirect_back. rails-source-path can hanlde this by explicily specifying the entry actions and remember the previous route in session store, hence can be used in the whole controller. Also a helper method is providered so it can be used in view like 'back' or 'cancel' button.