A gem to automate using outdated-browser with Rails >= 4.

Rapidly build Rails controllers.

Easily define <meta> and <link> tags. I18n support for descriptions, keywords and titles.

Pages.

The library to access the new services from Pagseguro (v2)

Allows a model of your choosing (such as users) to subscribe to a plan, which enables features.

LTI mountable engine

Panoptic adds a real time web interface on top of SolidQueue to monitor processes, queues and jobs

Processors for paperclip

Rails admin engine

SEO tools for the Para CMS

Parliament Utils gem.

Rails Engine to make internal routes searchable and discoverable for more than just the name of the route. All aspects of a route are searchable from the HTTP verb to the paramters a route supports.

Passbook pkpass creation and management for Ruby projects

Devise is awesome, but we don't need all that UI/UX for PassKeys. This gem is to make it easy to provide a back end that authenticates a mobile front end with PassKeys.

Pattern generator provides you with convenient commands to generate patterns in your Rails app.

Extensions and enhancements to Ruby's built in Logger class. Extensions include: multiple output streams, JSON formatting for easy aggregation, and a Railtie to set some sane(ish) defaults for production Rails environments.

pay_fu engine

A rails engine to integrate Paymill subscriptions within your Rails 4.1.6 application, out of the box

Allows customization of: * Specify which level of notification you would like with an array of optional styles of notification (email, webhooks) * the sender address of the email * the recipient addresses * the text used to prefix the subject line * the HTTP status codes to notify for * the error classes to send emails for * alternatively, the error classes to not notify for * whether to send error emails or just render without sending anything * the HTTP status and status code that gets rendered with specific errors * the view path to the error page templates * custom errors, with custom error templates * define error layouts at application or controller level, or use the controller's own default layout, or no layout at all * get error notification for errors that occur in the console, using notifiable method * Override the gem's handling and rendering with explicit rescue statements inline. * Hooks into `git blame` output so you can get an idea of who (may) have introduced the bug * Hooks into other website services (e.g. you can send exceptions to to Switchub.com)