Makes SASS less of a hassle on read-only filesystems by compiling and serving it up for you

Makes SASS less of a hassle on read-only filesystems by compiling and serving it up for you. Rails3 compatible from Papino's fork on Github.

A simple way to check your app heart.

This gem is designed for use by Rails applications running on Heroku. For others, the better approach is to use a frontend server such as nginx or Apache. However, the Heroku Cedar stack is no longer fronted by a file server, and there is no automatic provision for gzipping responses. This gem ac...

Generate API documentation from JSON Schema.

Allows arbitrary reporting on your ledger using easy-to-write SQL queries

Lowkiq

Mayu Live is a live updating server side VirtualDOM framework for Ruby, inspired by modern frontend tools that exist in the JavaScript ecosystem.

Add SQL like auto-incrementing fields to your Mongoid documents.

A cross-platform Pact verification tool to validate API Providers. Used in the pact-js-provider project to simplify development

Graphite dashboard frontend

Web automation DSL on top of webdriver and nokogiri

In version 5.0 the authors of the popular Ruby web server Puma chose to remove the daemonization support from Puma, because the code wasn't wall maintained, and because other and better options exist for production deployments. For example systemd, Docker/Kubernetes, Heroku, etc. Having said ...

Rack::Brotli enables Google's Brotli compression on HTTP responses

Rack::Debug is a middleware that provides a simple interface to ruby-debug. Helps debug apps running in Passenger.

Rack::Debug adds a middlerware interface to ruby-debug http://github.com/github/rack-debug

provides a simple endpoint for your rails app for a heartbeat client to connect to

JSON Schema based Rack middlewares

Rack middleware that provides authentication based on JSON Web Tokens.

Rack-P3p is rack middleware for inserting P3P headers into apps. This will allow your application to serve cookies to IE when in an iframe. It will also pull off the cookie on 304 responses, since IE does not like the cookie then.